hello,


I would like to setup a dns for my department and I want it to query my company's main DNS for any query that it can't answer itself. The way my environment is set up is this hostname.xxx.yyy.org. So I want it to answer any query that pertains to "hostname" and then refer any other query relating to outside this domain to the xxx's main dns server. I have initally set it up but but for some reason everytime I query hostname by itself it looks into my hosts table and then goes to the dns I have setup. So primarily I want it to resolve the fullly qualified hostname: aaa.bbb.ccc.org without using /etc/hosts.

Any help is greatly appreciated.


Thank you,


Jay

Add 'search xxx.yyy.org' to the end of /etc/resolv.conf and make sure /etc/host.conf reads 'order bind, hosts'

you can try it : edit
1. /etc/named.conf (forwad and reverse also master or slave)
2. /var/named/exampleforward and /var/named/examplereverse
3. /etc/resolve (bind or hosts firstly )
4. /etc/host.conf

Thanks for the replies. I got the DNS working and I placed in the search option in /etc/resolv.conf but I was trying to avoid this because we have hetrogenous environment with Unix, Linx, Windows, MacOS and BeOS environment. So I am now trying to find out a way so that the DNS can automatically resolve the fully qualified domainname when I only give it a hostname (instead of hostname.aaa.bbb.org which seems to work...but just too lazy to type all that).
So right now when I try to query a box with no search entry in /etc/resolv.conf I get:

[root@server1 ~]# ssh linuxbox1
ssh: linuxbox1: Name or service not known

and when I place in the /etc/hosts or search entry in /etc/resolv.conf file it resolves fine. So there must be a way for me to place this option in the DNS configuration.

Thanks,

Jay

If I understand what you are asking, you are in an environment where the domain is xxx.yyy.org and you want to resolve addresses like foo.xxx.yyy.org by just using the hostname foo instead of the fully qualified domain name foo.xxx.yyy.org? This is an issue to be worked out on the clients, not the DNS server. The fixes previously suggested change the way the client decides how/when to use the DNS server to look up a name. Some of these can also be set, for DHCP clients, from the DHCP server. On a Linux DHCP server, you can add these global settings to the dhcpd.conf file to let the clients know they are on the xxx.yyy.org domain so they will assume that given a hostname alone to look up, it will be one on this domain and query it's DNS server: