Make sure the DC is pointing to either itself or another AD int. DNS server. Next restart the netlogon service and then from the cmd prompt ipconfig /registrerdns. Make sure all clients point to the server for dns.
How many DC's do you have? ----- Original Message ---- From: James Edwards <[EMAIL PROTECTED]> To: NT System Admin Issues <[email protected]> Sent: Tuesday, May 27, 2008 6:07:14 PM Subject: Re: Hosed DNS?? James Edwards wrote: > Kennedy, Jim wrote: >> First hit the DC's with a command prompt and use ipconfig /registerdns >> >> >> > Am I going to get lucky and it's that simple to rebuild the > "_ldap_tcp.dc_msdcs.my.domain" entry?? > I guess I'll know in about 15 minutes. > > THANKS > Guess I didn't get that lucky. The Counter Spy console still gives a "a root AD doesn't exist or couldn't be contacted". Everything was working 'till last Friday. Jim ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
