The only problem with that is creating a DNS Island.  Why not have the DNS servers point to each other to avoid that problem?  Not knowing the way in which they are connected (T1, 56K dialup, etc) it would be hard to answer that question.

 

You can also configure DNS to point to itself and forward all other queries to the Singapore DNS Server.

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark
Sent: Thursday, April 22, 2004 9:58 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] DNS Server Using its own IP as a Primary DNS

 

Wasn’t this one on the exam? The cities sound familiar…;-)

 

Anyway, why force a DC to go elsewhere for its DNS info – just make it query itself and make DNS AD-integrated.

 

<mc>

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 22, 2004 9:43 AM
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

Reply via email to