Configuring a Linux BIND server to act as a secondary DNS server to AD is easy. I suggest adding your Linux system to your AD zones as a nameserver, and allowing replication from any nameserver for each zone.
Here's the basic steps:
Install BIND on your Linux system
Configure basic BIND options, add all your zones from AD as shown here:
zone "yourzone.com" {
type slave;
masters {
10.20.30.40;
};
file "/var/named/slaves/yourzone.com.hosts";
};
Repeat this zone configuration for all zones in AD - forward and reverse zones. If you have conditional forwarders, you can set them up like this:
zone "otherdomain.com" {
type forward;
forwarders {
1.2.3.4;
2.3.4.5;
};
};
This will not send these conditional forwarder zones to AD, you're just configuring them to be a conditional fowarder on BIND. Same difference.
I also let my BIND server be a caching nameserver for all other domains, so it won't be entirely dependant on AD.
Now start BIND, and give it a few minutes to start replicating. You can now use it as a secondary DNS server, and it can be added to your DHCP options or whatever you need.
I use this type of setup and have seen no problems with it.
This is a very broad question. Go to http://www.isc.org/software/bind and read, read and read. Then install Linux and bind and try it. When you have more specific questions come back and ask.
– rems – 2011-02-18T17:42:23.613And you may run into more headaches if you remove AD Integrated DNS and switch to plain DNS – charlesbridge – 2011-02-18T19:46:32.313