RE: [ActiveDir] 2003 DNS

[Rocky Habeeb]

From: 291382 "Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS" (Notice the title "Both 2K and 2K3)   Question: What are the common mistakes that are made when administrators set up DNS on network that contains a single Windows 2000 or Windows Server 2003 domain controller? Answer: The most common mistakes are: • The domain controller is not pointing to itself for DNS resolution on all network interfaces   Question: How do I set up DNS for other domain controllers in the domain that are running DNS? Answer: For each additional domain controller that is running DNS, the preferred DNS setting is the parent DNS server (first domain controller in the domain), and the alternate DNS setting is the actual IP address of network interface. RH _______________________________________________  Debbie,   True for Windows 2000 as well.  Let me see if I can find the doc for you.  It’s not an issue – it’s the recommended practice.  Are you thinking of the potential ‘forest island’ problem where a child domain can become orphaned from the forest records if it doesn’t secondary the _msdcs.blah.blah.blah records?   Here’s that promised KB.  http://support.microsoft.com/default.aspx?scid=kb;en-us;825036   -rtk   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ellis, Debbie Sent: Wednesday, May 11, 2005 12:18 PM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] 2003 DNS    I thought I read about an issue with having a 2003 DNS server pointing to itself as the preferred or primary DNS Server.  Has anyone heard about this issue and if so, where can I find documentation on it?