Windows Forum

Ask something
Discussion Locked

Remove Previous Domain Leftovers

0 helpful
8 replies

by dwdino

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I currently have a W2K DC which continues to have error number 5775 (Deregistration of the DNS record...).

History:

This server was in a test lab approx 4 weeks ago. It was a DC of a "dummy" domain on which testing was done. The server was cleaned up (exchange & toptools uninstalled), demoted, and moved to workgroup.

This was believed to have removed all instances of previous domain from server.

The server was then added to the "live" domain and promoted to DC. Approx 2 days later,netlogon started generating the 5775 error continually.

I added DNS to the services which NetLogon must wait upon per MS KB article. This did not change the issue one bit.

The errors contain the following from the previous test domain of thisserver:
gc._msdcs.(domain)
_gc._tcp.Default-First-Site-Name._sites.(domain)
_kerberos._tcp.Default-First-Site-Name._sites.(domain)

It appears to be attempting to remove old DNS records. These records are non-existant on the "live" domain. I have purged the registry of any and all references to the previous domain. I have deleted and reinstalled DNS services on this server twice. I have searched AD for any mention of previous domain.

All to no avail. I do not want to spend an entire weekend reinstalling and reconfiguring this server.

Please, any ideas on how to remove these lingering pieces.

8 replies

by quintar51

when you uninstall DNS, make sure you delete the DNS folder in c:\winnt\system32. Then reinstall it. The only other place any remains will be is the registry, which you've searched.

What about the domain suffix for the machine?
It should be the "live" domain, but it's worth checking. Right-click My Computer, Network Identification, Properties, More button.

by joseph moore

Here is a picec of Technet article 255913:

"Additionally, a DC will attempt to register the A record(s) listed in its Netlogon.dns file in the root zone (for example reskit.com). In this case, because the root zone is located on a non-dynamic DNSserver, these updates will not succeed.
Every Windows 2000 DC has a Netlogon.dns file located in its %SystemRoot%\System32\Config folder. This file contains a list of DNS records that the DC will attempt to register when the Netlogon service starts."

I was working on a similar thing last week (setting up a new Win2K DC in a lab) and this is how I found out about this file.

So, I would go to c:\winnt\system32\dns and look for this file, NETLOGON.DNS and open it up. I bet your problem is there. The old DNS records from your lab setup.

You can either a) delete the incorrect records out of the file, or b)
"The following registry key should be used to disable the DC from attempting to register the A records seen in the Netlogon.dns file.

Set the REG_DWORD RegisterDnsARecords value to 0 (zero) under:
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
"

hope this helps

by dwdino

If I could find you I would kiss your neck so hard it would a hickey!! LOL
Thanks a million!
To the victor goes the spoils...

by timwalsh

I would suggest booting into Directory Services Restore Mode and running ntdsutil. Use the metadata cleanup option, which is designed to purge AD of objects related to decomissioned servers.

This discussion is closed to new replies.