RE: [ActiveDir] DNS Server Using its own IP as a Primary DNS

[Roger Seielstad]

Personally, even though its officially resolved, I still don't completely trust it - and there's such a low overhead with making the DC's nearest neighbor its DNS server that its not detrimental if done.   I also tend to have 2 DCs in each location that rates a DC, so they point to each other first, and an offsite one second.   Roger -------------------------------------------------------------- Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc.   From: Peter Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 10:46 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [ActiveDir] DNS Server Using its own IP as a Primary DNS As far as I’m aware the issue with a DNS server pointing to itself was only an issue in Windows 2000 in the forest root domain. The issue was referred to the poisoned  island problem and as been resolved in Win2K3. If this domain is not the forest root then there should not be an issue. However I would think that the best thing to do would be to point it to self and configure the forwarders as the machines in Singapore. Anyone else have an opinion?   Peter Johnson DBSA Mobile: +27 833060019 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 22 April 2004 15:43 To: [EMAIL PROTECTED] Subject: [ActiveDir] DNS Server Using its own IP as a Primary DNS   Hi All, I have 2 remote sites, one in Singapore and the other in Sydney. I am going to configure a new DC/DNS/GC for Sydney. Singapore has 2 domain controllers running DNS. The new system in Sydney uses the DC's in Singapore as it's primary/secondary DNS. After I run DCPROMO and configure DNS on the Sydney box, should I continue pointing to Singapore, or should I have the system point to it's own IP as primary DNS. I have heard two schools of thought on this issue, and just wanted to get an opinion. Thanks, -Jbl