New tree DNS problem in existing forest
Posted on 2010-09-06
In a test environment, I have two forests: abc.local and ghi.local.
Forest abc.local contains two trees:
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?