Jim, Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 Regards, Austin "Jim" <nospam@any.time> wrote in message news:e5w9f38IIHA.5764@TK2MSFTNGP06.phx.gbl... Thanks for your continuing help with this. Below is the dcdiag /test:dns from the only DC that has errors. It's better than it was. No mutltihomed DCs. Root hints are still default on the DNS servers

Thanks for your continuing help with this. Below is the dcdiag /test:dns from the only DC that has errors. It's better than it was. No mutltihomed DCs. Root hints are still default on the DNS servers. Forwarders are active. GPOTool shows 15 policies, all OK. I did also reset the TCP/IP stack on the problem server, no change. Domain Controller Diagnosis Performing initial setup: Done

Hi Jim, When you have deleted the zone, rt click forward zones and select "new zone". Call it _msdcs.<DomainName>. Then in your Domain Forward lookup zone, rt click and select "new delegation". Call the new delegation "_msdcs". Regards, Austin PS Remember to make them AD integrated zones. "Jim" <nospam@any.time> wrote in message news:%%233Lrm7vIIHA.2268@TK2MSFTNGP02.phx.gbl.

Hi Jim, Recreating the zone would not damage AD. You can also recreate the _msdcs.domain.com zone and create the delegation in domain.com. DCs should reregister their records when bounced. Regards, Austin "Jim" <nospam@any.time> wrote in message news:%%23GoabMkIIHA.4476@TK2MSFTNGP06.phx.gbl... Hi, Thanks. If I deleted the domain.com zone altogether then recreated it would

Hi Jim, You need to get your DNS config sorted out before any replication or DC locator issues are resolved. You seem to have root hints and forwarders configured on this DNS Server. They are mutually exclusive settings. One or the other. So delete the root hints. And the root zone. Also, the "Broken delegated domain error occurs when you have a zone for domain.com.domain.com (???) and