DNS configuration - unable to contact DC

[Glennn]

I'm building a w2k network. I have 1 server with AD running. I'm trying to promote a 2nd server to a DC to run RIS. DCPromo reports it can't find the domain that it is already part of ?

I checked MS. They confirm DNS problems with SRV records so I followed directions to the letter - I deleted the zone, recreated it (with dynamic updates), stopped/started NETLOGON and rechecked my Zone. Still it does not create the subfolders (_msdcs, _sites, _tcp, _udp) within the forward lookup zone. I assume this why the member server cannot contact it's own domain (I can ping the AD server by name and IP).

What am I doing wrong or missing ?

 

[BLarson]

I don't know if this will help, but I had a similar problem with workstations joining a domain and they couldn't find it. I had an LMHOSTS file on the workstations (still have some NT 4 servers on the network). Deleting the LMHOSTS file allowed it to see/join the domain.

If you don't have and LMHOSTS on the member server this will be of no help to you.

 

[Glennn]

problem solved turned out DNS was corrupt. Fixed with netdiag