Sponsored Content
Operating Systems Linux Red Hat DNS A-Record point to another DNS Post 302559262 by mark54g on Monday 26th of September 2011 02:43:16 PM
Old 09-26-2011
It depends on what operating system that the client uses. The resolv.conf on Linux can contain a set of domains to append, in order, when searching for non FQDN names in the lookup.

Windows has a similar construct, but I am unsure of how that is implemented.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Dns

I would like to set up a DNS on my system, just to learn really, how difficult and what all is involved in the set up? How difficult? (6 Replies)
Discussion started by: jo calamine
6 Replies

2. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

3. UNIX for Dummies Questions & Answers

Configuring DNS MX record

I now know that I have to configure dns mx to actually be able to send email correctly to my mail. I have the link(user guide) on how to do this : http://bobcares.com/blog/?p=29 but where do I configure it? Is there a specific file for the configuration? I really don't understand this part. (2 Replies)
Discussion started by: anaigini45
2 Replies

4. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

5. IP Networking

DNS does all slave Name Server must be in the zone Resource Record file?

Hy guys, I've a problem configuring my Name Server (using bind 9) which is I'ts always necessary to put all slave Name Server for a zone in the zone resource record file or db (as you prefer)? I've this scenario: A - my domain which is son of some TLD and I delegated into two new domains B... (1 Reply)
Discussion started by: pharaoh
1 Replies

6. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

7. UNIX for Dummies Questions & Answers

How to Create a new internal DNS CNAME record

I need to create a new internal DNS CNAME record called "project.omc.eod" that points to a server called SPARC27.ds.eod. This is my first time doing this and any help would be greatly appreciated. Thanks in advance (10 Replies)
Discussion started by: mikeade
10 Replies

8. Red Hat

[Solved: Missing A Record] DNS issue

Hi, I have recently built a new DNS server and created a new zone. I use an ESMTP server to handle mail and the new domain has been added to this. I can send mail to gmail and other domain addresses but unable to send it to one particular domain. (DSN:Service Unavailable) DNS... (2 Replies)
Discussion started by: Duffs22
2 Replies

9. UNIX for Dummies Questions & Answers

How to update DNS record in Solaris 5.10?

Hi I have a DNS server running on Solaris 5.10, I need to update ip address of two urls defined on our dns server how do i do that? and do i need to restart dns/named service after? how do i restart the service? Thanks (4 Replies)
Discussion started by: arocker
4 Replies

10. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
HOST.CONF(5)                                                Linux System Administration                                               HOST.CONF(5)

NAME
host.conf - resolver configuration file DESCRIPTION
The file /etc/host.conf contains configuration information specific to the resolver library. It should contain one configuration keyword per line, followed by appropriate configuration information. The following keywords are recognized: trim This keyword may be listed more than once. Each time it should be followed by a list of domains, separated by colons (':'), semi- colons (';') or commas (','), with the leading dot. When set, the resolver library will automatically trim the given domain name from the end of any hostname resolved via DNS. This is intended for use with local hosts and domains. (Related note: trim will not affect hostnames gathered via NIS or the hosts(5) file. Care should be taken to ensure that the first hostname for each entry in the hosts file is fully qualified or unqualified, as appropriate for the local installation.) multi Valid values are on and off. If set to on, the resolver library will return all valid addresses for a host that appears in the /etc/hosts file, instead of only the first. This is off by default, as it may cause a substantial performance loss at sites with large hosts files. reorder Valid values are on and off. If set to on, the resolver library will attempt to reorder host addresses so that local addresses (i.e., on the same subnet) are listed first when a gethostbyname(3) is performed. Reordering is done for all lookup methods. The default value is off. ENVIRONMENT
The following environment variables can be used to allow users to override the behavior which is configured in /etc/host.conf: RESOLV_HOST_CONF If set, this variable points to a file that should be read instead of /etc/host.conf. RESOLV_MULTI Overrides the multi command. RESOLV_REORDER Overrides the reorder command. RESOLV_ADD_TRIM_DOMAINS A list of domains, separated by colons (':'), semicolons (';') or commas (','), with the leading dot, which will be added to the list of domains that should be trimmed. RESOLV_OVERRIDE_TRIM_DOMAINS A list of domains, separated by colons (':'), semicolons (';') or commas (','), with the leading dot, which will replace the list of domains that should be trimmed. Overrides the trim command. FILES
/etc/host.conf Resolver configuration file /etc/resolv.conf Resolver configuration file /etc/hosts Local hosts database NOTES
The following differences exist compared to the original implementation. A new command spoof and a new environment variable RESOLV_SPOOF_CHECK can take arguments like off, nowarn, and warn. Line comments can appear anywhere and not only at the beginning of a line. Historical The nsswitch.conf(5) file is the modern way of controlling the order of host lookups. In glibc 2.4 and earlier, the following keyword is recognized: order This keyword specifies how host lookups are to be performed. It should be followed by one or more lookup methods, separated by com- mas. Valid methods are bind, hosts, and nis. RESOLV_SERV_ORDER Overrides the order command. Since glibc 2.0.7, the following keywords and environment variable have been recognized but never implemented: nospoof Valid values are on and off. If set to on, the resolver library will attempt to prevent hostname spoofing to enhance the security of rlogin and rsh. It works as follows: after performing a host address lookup, the resolver library will perform a hostname lookup for that address. If the two hostnames do not match, the query fails. The default value is off. spoofalert Valid values are on and off. If this option is set to on and the nospoof option is also set, the resolver library will log a warn- ing of the error via the syslog facility. The default value is off. spoof Valid values are off, nowarn, and warn. If this option is set to off, spoofed addresses are permitted and no warnings will be emit- ted via the syslog facility. If this option is set to warn, the resolver library will attempt to prevent hostname spoofing to enhance the security and log a warning of the error via the syslog facility. If this option is set to nowarn, the resolver library will attempt to prevent hostname spoofing to enhance the security but not emit warnings via the syslog facility. Setting this option to anything else is equal to setting it to nowarn. RESOLV_SPOOF_CHECK Overrides the nospoof, spoofalert, and spoof commands in the same way as the spoof command is parsed. Valid values are off, nowarn, and warn. SEE ALSO
gethostbyname(3), hosts(5), nsswitch.conf(5), resolv.conf(5), hostname(7), named(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 HOST.CONF(5)
All times are GMT -4. The time now is 10:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy