Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've set up a replica DC in a remote location. It's connected to the main site through a VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC:

Running enterprise tests on : mydomain.co.uk

      Starting test: LocatorCheck

         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355

         A Global Catalog Server could not be located - All GC's are down.

         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355

         A Primary Domain Controller could not be located.

         The server holding the PDC role is down.

         ......................... mydomain.co.uk failed test LocatorCheck

Is it giving this error just because it is not the global catalogue server, or is there some connectivity issue where it does not think there is one at all, as the error seems to imply? If so, it seems odd, as all other tests were passed.

What do I do about this?

share|improve this question
    
How's DNS set up on the replica? –  Shane Madden Mar 16 '12 at 2:58
    
@ShaneMadden: It was set up through netdom join. I assumed that was all that was needed. The DNS entries appear to have been replicated, apart from the DCs themselves (the original DC appears on both DNS databases, but the replica only appears through dig on the original, but with two entries, one being an out-of-date address). –  paradroid Mar 16 '12 at 3:24
1  
Are you in some kind of recovery scenario? The server is doing SRV record lookups to try and find the server holding the PDC Emulator FSMO role as well as looking for a Global Catalog server. I believe Shane was referring to the DNS client settings on the NIC of the remote server. –  SpacemanSpiff Mar 16 '12 at 3:42
    
@SpacemanSpiff: I corrected the DNS discrepency I mentioned above, but I still get the error. No, it's just a new replica, not a recovery. I just checked the DNC client settings. They original DC is set to 127.0.0.1 only and the replica is set to an external public DNS server as primary and 127.0.0.1 as secondary. I'll remove the external entry, but should they also include each other as the second entry? As they have replicated DNS databases, would that even make a difference? –  paradroid Mar 16 '12 at 4:05
2  
in 2003 and later, you should always point to 127.0.0.1, and then secondary to another domain controller or any other DNS server with that internal DNS zone available. You should then add a "forwarder" to the DNS service itself under the DNS MMC snap-in. –  SpacemanSpiff Mar 16 '12 at 4:23

2 Answers 2

up vote 4 down vote accepted

Check the DNS settings on your new domain controller, in 2003 and later, you should always point to 127.0.0.1, and then secondary to another domain controller or any other DNS server with that internal DNS zone available. You should then add a "forwarder" to the DNS service itself under the DNS MMC snap-in.

share|improve this answer
    
Just a minor correction, 127.0.0.1 should always be last especially in 2003 where it was possible to create a replication island. –  MDMarra Jul 7 at 3:32
    
Seems like the tune on how best to do this changes, again, and again, and again. –  SpacemanSpiff Jul 8 at 17:39

I have same problem on windows 2008 enterprise 32 bit server, had tried whole day, and finally i see the service one by one and started services which i think is vital and finally i restarted the Active directory services on server and my problem was solved and DNS again started working perfectly.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.