Sponsored Content
Operating Systems Linux Ubuntu Linux Redhat ES 4.0 - DNS Config Issues Post 302072337 by Neo on Monday 1st of May 2006 04:54:38 PM
Old 05-01-2006
You may not have your /etc/resolver.conf file set up correctly and are simply picking up a host from the default /etc/hosts file.

Where is your nameserver running?
 

10 More Discussions You Might Find Interesting

1. Solaris

DHCP DNS Config

I'm running Solaris 9 and I need my box to request it's DNS servers off a DHCP server - can I do this? (1 Reply)
Discussion started by: Jdogg
1 Replies

2. UNIX for Advanced & Expert Users

dns issues

Just recently we have been having some dns issues. Some websites won't work i.e. (www.msn.com, aimexpress.aim.com...) I have manually put A records in my named.db file and in the hosts file to try to get it to work but still they do not work. I have looked up updating my named.ca file for the... (1 Reply)
Discussion started by: rickyt00
1 Replies

3. UNIX for Dummies Questions & Answers

Redhat DNS Entry

I have a installed Redhat Linux v5 on a new HP Pavillon PC. It has a dual boot with Vista. Booting from Vista, I can connect to the internet. However with Redhat I cannot connect to the internet. I looked at the /etc/resolv.conf file in Redhat and there is no DNS entry there. From where do I... (28 Replies)
Discussion started by: AnilAnand
28 Replies

4. IP Networking

DNS Cache-Only Config Advice

Hi Chaps and Chappettes, I've had a short period of time recently to learn and implement DNS cache-only in our organisation. Trouble is, according to my tcpdumps, the amount of traffic on port 53 has increased. This is of course the exact opposit of the desired effect. Would y'all mind looking... (2 Replies)
Discussion started by: danny.hudson
2 Replies

5. 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

6. Red Hat

DNS for linux RedHat

Dear members, I am trying to set up a simple DNS but the problem is that when I ping the name of the IP address in the Reverse file, it does not recognise it. My code are as follows: Note that my IP address is 172.22.45.237. In my /etc/named.conf file, I have added the following lines ... (10 Replies)
Discussion started by: shakshakshuk
10 Replies

7. IP Networking

Configuring DNS Server in Linux Redhat

Can someone help with a detail step-by-step oh how to configure DNS server on Linux Server. - I need to have 3 IP addresses map to a single hostname. for clients I'm a Linux rookie. Thanks Oscar (1 Reply)
Discussion started by: FrankOscar
1 Replies

8. Red Hat

RedHat Linux GUI Issues

hi all i have installed Windows 7 first. then i installed linux on dual partations... i am booting both of them through dual boot... but when i start linux its only working well with CUI, when i used commands like startx or changed the initd to 5 then its loading the GUI interface of RedHat... (9 Replies)
Discussion started by: Nikhil Dethe
9 Replies

9. IP Networking

DNS config preventing mail delivery

Hi Please can you help on this: the Net Admins decided to use DNS to resolve names, so this is preventing mail being delivered when using commands like date | mailx -s "test" abc.xyz@asdf.xx.yy. What we were asked was to edit /etc/resolv.confand add 3 entries, in all servers (10 Replies)
Discussion started by: fretagi
10 Replies

10. Red Hat

Issues installing inotify-tools on RedHat Linux

I wish to install inotify-tools-3.20.1-2.4.x86_64.rpm on Linux and fire inotifywait command. Initially i was looking for "inotify-tools-3.xx.tar.gz" as instructed here http://jensd.be/248/linux/use-inotify-tools-on-centos-7-or-rhel-7-to-watch-files-and-directories-for-events I have... (9 Replies)
Discussion started by: mohtashims
9 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 08:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy