DNS Setup for Multi-domain forest

I've heard different opinions on where a Server 2003 DC should point to for its preferred and alternate DNS servers in a multi-domain forest.

In my forest, I have a root domain with 4 DCs, and 4 subdomains with 2 DCs each, they are all W2K3.  The majority of the DNS zones are setup as AD integrated, one is a primary, and a few are secondary.  All the DCs are housed under the same roof so there are no slow connections to remote locations to deal with.

I've read that the DCs in the subdomains should point to themselves as the preferred DNS server and then to their mate as the alternate.  Would the same apply to the root DCs where DC1's alternate is DC2, DC2's alternate is DC3, DC3's alternate is DC4, and DC4's alternate is DC1?

Is there any risk of the DC becoming an "island"?  I read that this was only an issue with W2K and not W2K3.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

There is no law that says a DC can only have 2 DNS servers configured.  If you wish, you can have every DC pointed at itself, as well as the other three, for DNS servers.

As far as a DC DNS server becoming an "island", that might possibly happen in the unlikely event that replication is broken in your environment.  If your AD is healthy, and all your zones are Active-Directory integrated zones, that shouldn't happen even if you have your DNS servers set up in the "daisy-chain" scenario that you describe.

Keep in mind that all DCs replicate with each other, whether it is a DNS "partner" or not.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Leon FesterSenior Solutions ArchitectCommented:
I've always pointed my DC's to themselves, however since reading this article which was recently highlighted to me on another forum I've started reconsidering my options.

According to the MVP(Mike Kline) who directed me to this post, he doesn't point Primary DNS to itself but rather points self as secondary and employing the loopback address as opposed to the static of the machine. He also claims to have run into several "race condition" issues when pointing primary DNS to itself.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.