Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 {
            <external DNS server IP 1>;
            <external DNS server IP 2>;
            };
    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;
            };
    };
share|improve this question
1  
What do the log files on the AD server say? I'd trace the DNS traffic between the bind and AD to see what is actually happening. –  Mark Wagner Dec 27 '10 at 18:15

2 Answers 2

up vote 1 down vote accepted

Please turn on logging on named - edit named.conf:

logging{ channel simple_log {
file "/var/log/named/bind.log" versions 3 size 5m;
severity warning;
print-time yes;
print-severity yes;
print-category yes; };
category default{ simple_log;
};
};

then:

  1. named-checkconf <path to your named.conf>
  2. rndc reconfig
  3. tail -f /var/log/named/bind.log

Observe what client is asking for? What server is sending? You have to be sure that AD is configured to receive requests from this server. Good luck!

share|improve this answer

I think you're making it too complicated. By default, AD DNS only does DNS queries within the AD domain, so all you need to do is tell it to automatically forward the remaining queries to your regular DNS server.

You do this by going into the dnsmgmt tool, select your domain controller, right click on it, and select "properties" then go to the "Forwarders" tab.

Make sure "DNS Domain" is set to "All other DNS domains" and then add your caching DNS server as a forwarder.

Should be a lot easier than trying to configure it upstream.

share|improve this answer
    
Unfortunately, I cannot do it that way. I run some pretty busy hosted mail/SPAM servers generating a high volume of DNS queries. For performance, I need the requests to be sent directly to the caching servers. –  Alex Dec 27 '10 at 17:04

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.