MS really likes to confuse people and use their own terms for things that are already existing.
An AD domain name must map to a DNS domain, which is also called a zone.
So AD Domain = IP DNS Domain = IP DNS Zone.
So you have two "separate" networks/locations that have the same domain name, but are using their own unique primary DNS servers.
The admins at the two sites need to work out who is really going to "own" DOMUS.com. The other site can be a secondary DNS server for that zone/domain.
Since the Atlanta site is using DOMUS.com as their AD domain name, they should be the primary for that zone/domain. The Memphis should have their DNS setup to be a secondary DNS server for that domain/zone.
Main Topics
Browse All Topics





by: oBdAPosted on 2009-11-06 at 10:59:39ID: 25761968
The only thing you can do about it is to move all the DNS entries currently in domus.com in Memphis to the server in Atlanta.
Then either
- remove the domus.com zone in Memphis, and setup conditional forwarding for domus.com in Memphis to point to your AD servers, or
- delegate the domus.com zone in Memphis to your AD DNS servers, or
- set it up as a secondary zone for your primary AD domus.com zone.