DNS errors after domain controller rename

  • Thread starter Thread starter Tim Ryter
  • Start date Start date
T

Tim Ryter

Greetings:

We recently renamed a domain controller running Windows 2003 in native
mode (I cannot find a "Windows2003.dns" group so if there is a more
appropriate place to post this please let me know). After the rename I
am getting the following event in the DNS Server event log:

Source: DNS
Category: None
Event ID: 7053
Description:
The DNS server sendto() function failed. The event data contains the
error.

Of course Technet doesn't say anything about this specific event, but I
did find some things about this event on technet but for NT 4.0. I'm
not sure if the process of cleaning the cache on that article applies to
my situation.

http://support.microsoft.com/kb/244132/en-us

This is the only domain controller with this issue and it began
immediately after the rename. The events appear to show up at random
times and have been relatively consistant since the rename (5-6 events
per day). I can't really find anything else wrong with the DNS server
besides the presence of this event. DNS records appear to be
replicating from that server to other AD servers in the domain and vice
versa. DNS lookups work correctly and I have had no complaints from
users.

Any help would be much appreciated.

TIA

Tim
 
Tim said:
Greetings:

We recently renamed a domain controller running Windows 2003 in native
mode (I cannot find a "Windows2003.dns" group so if there is a more
appropriate place to post this please let me know). After the rename
I am getting the following event in the DNS Server event log:

Source: DNS
Category: None
Event ID: 7053
Description:
The DNS server sendto() function failed. The event data contains the
error.
Click to expand...

http://www.eventid.net/display.asp?eventid=7053&eventno=727&source=DNS&phase=1
 
Tim said:
I did see that on eventid.net, however those articles refer to the
Windows NT 4.0 problem and a patchable problem on Windows 2000. None
seem to directly relate to the problem I'm having on Windows 2003
(unless you believe the process outlined for NT 4.0 applies to
Windows 2003).
Click to expand...

All of the articles seem to point to a corrupted or missing cache.dns file.
Replace the cache.dns file in the %systemroot%\system32\dns directory from
the %systemroot%\system32\dns\backup directory.

Replacing root hints with the Cache.dns file
http://support.microsoft.com/kb/249868/en-us
 
All of the articles seem to point to a corrupted or missing cache.dns
file. Replace the cache.dns file in the %systemroot%\system32\dns
directory from the %systemroot%\system32\dns\backup directory.

Replacing root hints with the Cache.dns file
Click to expand...

Kevin,

I followed the instructions in KB 249868 and everything worked except
the RootDNSServers container did not recreate in our Active Directory.
Everything seems to work including external name resolution, however I'm
uneasy with that container missing. What do you suggest doing to get
that recreated? Should I do an authoritative restore?

Any help would be appreciated.

Regards,

Tim R
 
Tim said:
Kevin,

I followed the instructions in KB 249868 and everything worked except
the RootDNSServers container did not recreate in our Active Directory.
Everything seems to work including external name resolution, however
I'm uneasy with that container missing. What do you suggest doing to
get that recreated? Should I do an authoritative restore?
Click to expand...

I don't think the RootDNSServers container is a big problem or even an
issue, unless you have a Root Zone. In all likelihood you don't want or need
a root zone.
 
is your dns server accepting thre new name ?if yes try to flush the
name of your DC from AD records using metadata switch in ntdsutil tool?
see if that works.....
 
IS YOUR DNS SERVER ACCEPTING THE NEW NAME OF YOUR DC? IF NO, TRY
FUSHING THE OLD DC NAME FROM ACTIVE DIRECTORY RECORDS USIN THE metadata
SWITH IN ntdsutil TOOL.THEN RESTART THE SYSTEM .SEE IF THAT WORKS.....
 
I don't think the RootDNSServers container is a big problem or even an
issue, unless you have a Root Zone. In all likelihood you don't want
or need a root zone.
Click to expand...

Well I don't see any problems so far, everything is running fine. Except,
the error messages never went away, I still get the sendto() errors in the
event log as before. It's also the only DC/DNS server I get that error
with. It has to have something to do with the rename, although I can't
find that it's really causing any problems.

In response to the other poster, yes everything works and the error seems
more of an annoyance then anything. I don't think the DC rename failed
really besides this annoying little side effect.

Thanks!
 
Back
Top