Post-Domain Rename - Old Domain Lingers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

A while back I renamed a Windows Server 2003 domain and I haven't been able
to get rid of the final references of the domain. I followed all the
documentation, did the metadata cleanup, removed the zones from the DNS, and
even cleaned up lingering service principal names on the domain controllers.
At this point I'm stuck with NETLOGON registering a warning every time it
starts (see below). I've deleted the netlogon.dns/dnb files and restarted
DNS servers, none of the three DNS servers are not referencing themselves,
and none of the connection IP settings are referencing the domain. NetDiag
doesn't like the old domain being around and consistently failed the DNS
test. Any thoughts on how I can get rid of the reference to the old domain?
---
Event Type: Warning
Event Source: NETLOGON
Event ID: 5781
Computer: DC1
Description:
Dynamic registration or deletion of one or more DNS records associated with
DNS domain 'olddomain.net.' failed. These records are used by other
computers to locate this server as a domain controller (if the specified
domain is an Active Directory domain) or as an LDAP server (if the specified
domain is an application partition).

Possible causes of failure include:
- TCP/IP properties of the network connections of this computer contain
wrong IP address(es) of the preferred and alternate DNS servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not running
- Preferred or alternate DNS servers are configured with wrong root hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration

USER ACTION
Fix possible misconfiguration(s) specified above and initiate registration
or deletion of the DNS records by running 'nltest.exe /dsregdns' from the
command prompt or by restarting Net Logon service. Nltest.exe is available
in the Microsoft Windows Server Resource Kit CD.
---
nltest /dsgetdc:newdomain.net

DC: \\dc1.newdomain.net
Address: \\192.168.1.10
Dom Guid: d54ae0d9-e650-4cc3-9a76-2ef993bb3460
Dom Name: newdomain.net
Forest Name: newdomain.net
Dc Site Name: Toronto-HeadOffice
Our Site Name: Toronto-HeadOffice
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC
DNS_DOMAIN
DNS_FOREST CLOSE_SITE
The command completed successfully
---
nltest /dsgetdc:olddomain.net

DC: \\dc1.newdomain.net
Address: \\192.168.1.10
Dom Guid: d54ae0d9-e650-4cc3-9a76-2ef993bb3460
Dom Name: olddomain.net
Forest Name: olddomain.net
Dc Site Name: Toronto-HeadOffice
Our Site Name: Toronto-HeadOffice
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC
DNS_DOMAIN
DNS_FOREST CLOSE_SITE
The command completed successfully
---
Thanks,
Colin


.

Relevant Pages

  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)
  • Re: Windows 2000 logon process
    ... Paul Williams ... when clients are accessing the GPO stored in SYSVOL during logon. ... PW>> Sound's like - that's a combination of DNS and Dfs client pointing ... Global Catalogue servers? ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... on 2 servers out of 4 DNS servers. ... DNS and 2003 DNS and how to set up Conditional Forwarding. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Howto refresh IIS 6 Application pool identity credential info
    ... You already have 80% of the work setup (DNS Aliases and HostHeaders) on the ... domain accounts (one for each layer) should be sufficient. ... The Application Servers are load balanced clustered, ... as the account name and SPN alias is correctly defined on both nodes. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ad and dns setup
    ... "Jorge Silva" wrote: ... domain It gave me 2 errors, no dns servers have dns records for this dc ... error no logon servers.. ... Make sure that the _msdcs zone exists and the scope is set ...
    (microsoft.public.windows.server.active_directory)