DNS caching server config problem
Posted
by
Alex
on Server Fault
See other posts from Server Fault
or by Alex
Published on 2010-12-27T15:34:56Z
Indexed on
2010/12/27
15:55 UTC
Read the original article
Hit count: 218
I have a Bind DNS caching-only server setup that is working. I am bringing up a new AD domain controller that will also be a DNS server for that AD but I don't want it responding to any DNS queries except those that are AD related. So, my goal is to leave this caching server as the primary DNS server for stations on the network and have it forward requests for the AD domain to the domain controller. My understanding is that I just need a forward zone for that domain pointing to the domain controller. However it does not seem to be working. So that leaves me to think that my caching server is not forwarding properly.
For example, this AD is going to have a naming convention of hostname.mydomain.local. If I do an nslookup and specify the domain controller's IP address as the server, I can query addresses that exist in DNS on that server, such as dc1.mydomain.local. However, queries to my caching server times out (I get a response from the caching server if I query mydomain.local but none of the objects in that domain).
Any suggestions? Here is my named.conf file:
options { directory "/var/named"; listen-on { 192.168.0.14; 127.0.0.1; }; forwarders { ; ; }; forward first; };
zone "." in { type hint; file "db.cache"; };
zone "0.0.127.in-addr.arpa" in { type master; file "db.127.0.0"; };
//forward zone for mydomain.local zone "mydomain.local" { type forward; forwarders { 192.168.1.21; }; };
© Server Fault or respective owner