New tree DNS problem in existing forest

In a test environment, I have two forests: abc.local and ghi.local.

Forest abc.local contains two trees:
   domain abc.local.
       subdomain sales.abc.local.
   domain def.local.

Replication, as tested by running repladmin /replsummary, appears to be working between all nodes.

The problem is with the def.local domain, which is a different tree in the abc.local forest.

When I look at the DC of def.local, everything looks fine, including DNS.

But in the DNS setup of the abc.local domain, it doesn't look right. For example, I can see the def.local domain, and it has the SOA and NS records for the servers in abc.local, but there are no A records. And the SOA for that domain is the DNS server for abc.local. If I manually add an A record pointing to the DC of the def.local domain, I still cannot do an NSLOOKUP or ping def.local and get replies.

Short of demoting the sole def.local server and then promoting it again, is there a simple fix for this? Or is this normal behavior?

Thanks.
ovidbaileyAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
NuttycomputerConnect With a Mentor Commented:
To get replication to move between domains you need to manually change the zone replication default from "All domain controllers in the Active Directory domain" to "All DNS servers in the Active Directory forest"

See the following technet article: http://technet.microsoft.com/en-us/library/cc779655%28WS.10%29.aspx

Additionally to answer your other questions in order to force a removal, will cause meta-data corruption that would need to be cleaned up later, you use the command dcpromo /forceremoval

http://technet.microsoft.com/en-us/library/cc787133%28WS.10%29.aspx

In addition this may be of interest to you. It refers to reinstalling a Dynamic DNS Active Directory Integrated Zone: http://support.microsoft.com/kb/294328
0
 
ovidbaileyAuthor Commented:
FWIW, if I force replication with repadmin /syncall, I get a msg from one item that says "The naming context is in the process of being removed or is not replicated from the specified server." Don't know that that means.
0
 
ovidbaileyAuthor Commented:
I have a little more info. The GC is stored on Server2.abc.local. When I ping the address of that server from the DC in def.com, I only get IPV6 replies. Looking at server2.abc.local's network settings, the primary DNS is pointing to the address of server1.abc.local (the first DC) and the secondary DNS is 127.0.0.1.
0
 
ovidbaileyAuthor Commented:
Solved the IPV6 issue by unbinding from the NIC. When I try to demote the server (which will remove this domain), I get an error that "Active Directory Domain Services could not transfer the remaining data in directory partition (abc.local) to Active Directory Domain Controller (this computer). "Could not find the domain controller for this domain."

Suggestions to either fix the original problem or figure out how to demote/ remove this domain?
0
 
ovidbaileyAuthor Commented:
Perfect reply to both issue. Thanks, Dude!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.