the dns server sendto() function failed. the event data contains the error. event id 77053
Hugo
How do I resolv this issue? I am looking up for help on various forums -
posting it here and hoping to get a resolution soon.
event id 7053
the dns server sendto() function failed. the event data contains the error.
Let me provide few details so that you can assist me better.
I have a Windows 2003 std AD box with DNS running for a while now. I decided
to have a backup AD win2k3 std with DNS on a VM (VMware).
I installed the OS/ DNS and later configured it as secondary DC via dcpromo.
I see the DNS zones were replicated almost instantly, but I noticed alls not
well and there were a few errors when I ran Netdiag and DCdiag (DC
Membership failed) and the Netlogon/Sysvol shares didnt show up on the
secondary DC.
However, I resolved them with the help from threads on various other forums.
As of now all looks fine - but in DNS events I see the
event id 7053
the dns server sendto() function failed. the event data contains the error.
I see that Microsoft has a fix for this error - but forums say its mostly
to supress it, I would like to know why Iam getting this error on my
secondary DC and not on my Primary DC and how to resolv it rather than
supress it.
Both my DNS servers dont do DNS forwarding as they are internal DNS
servers and I believe the root hints are correct (I see the same list of
root hint servers on the primary and secondary DC/DNS servers).
Appreciate help in resolving this issue. Pl let me know if I need to provide
further info.
Many thanks
Hugo
Ace Fekay [MCT]
news:%23I$%23waXYK...@TK2MSFTNGP05.phx.gbl...
What service pack version are the two DCs?
It sounds like the cache.dns file is corrupted. If you configure a
forwarder, do the errors go away?
What is the IP address in the error? Just 0.0.0.0?
When you look at the list of nameservers listed on the Root Hints tab, do
they match the names in the Cache.dns file, located in the
%systemroot%\system32\dns folder?
If not, go to DNS properties, Root Hints tab, and click the remove all of
the root hints. Then click on Copy from Server, and choose 4.2.2.2.
If it continues after thatm please read the following article. I kow it's
for Windows 2000, but if the above fail, this should work.
Replacing root hints with the Cache.dns file
http://support.microsoft.com/kb/249868
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Hugo
Thank you for the reply and sorry for the delayed response. I have given my
reply to your question below, Iam still getting the error.
Pl read below:
> What service pack version are the two DCs?
ANS: Service Pack 2
> It sounds like the cache.dns file is corrupted. If you configure a
> forwarder, do the errors go away?
ANS: Enabled the forwarders - did not make any difference - the errors still
persist
> What is the IP address in the error? Just 0.0.0.0?
ANS: I dont get any IP address in the error message
> When you look at the list of nameservers listed on the Root Hints tab, do
> they match the names in the Cache.dns file, located in the
> %systemroot%\system32\dns folder?
ANS: They both have the same entries
> If not, go to DNS properties, Root Hints tab, and click the remove all of
> the root hints. Then click on Copy from Server, and choose 4.2.2.2.
ANS: I get an error here - The specific DNS server cannot be contacted to
collect root hints.
verify that the machine is conencted to the network, and that the specific
remote dns server is conencted and running
> If it continues after thatm please read the following article. I kow it's
> for Windows 2000, but if the above fail, this should work.
> Replacing root hints with the Cache.dns file
> http://support.microsoft.com/kb/249868
ANS: I did according to the article - it did not help - however I will try
again.
Appreciate you help.
Hugo
Ace Fekay [MCT]
Hi Hugo,
I apologize for not seeing your response earlier. Are both UDP 53 and TCP 53
opened on the firewall? The reason I ask is because of the error you are
getting trying to update the Root Hints. I can't remember whether this
required UDP or TCP (I think it is UDP), but both ports should be opened.
Ace
Hugo
Thanks for the reply. No apologies, it was me who messed the reply to the
group :)
The windows firewall is turned off on both the DC's. Have a question here.
The DNS settings is the same for both the DC's, why is the second DC trying
to update its Root Hints? I dont see the error on my first DC.
Is there a way I can disable the secondary DC from checking for Root Hints
update ?
Many thanks
Hugo
"Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
news:u2DfiM8e...@TK2MSFTNGP02.phx.gbl...
Ace Fekay [MCT]
> Hi! Ace,
> Thanks for the reply. No apologies, it was me who messed the reply to the
> group :)
> The windows firewall is turned off on both the DC's. Have a question here.
> The DNS settings is the same for both the DC's, why is the second DC
> trying to update its Root Hints? I dont see the error on my first DC.
> Is there a way I can disable the secondary DC from checking for Root Hints
> update ?
>
> Many thanks
> Hugo
My question regards your edge firewall to the internet, not on the servers.
As far as your question, I am not sure. However, I am also not sure by what
you mean by "settings." There are *numerous* settings on a DNS server. One
little thing can be different.
I don't know if I had posted this between the different threads, but I
thought to post it for you just in case.
http://www.eventid.net/display.asp?eventid=7053&eventno=727&source=DNS&phase=1
It basically says that a nameserver entry is incorrect in the nameservers
tab, but I think you said they are correct?
Ace
Hugo
These DC are internal domain controllers. We cannot access internet from
these boxes.
I will go thru the url you provided and update you. Appreciate your help!.
Hugo
"Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
news:OVOTJRHf...@TK2MSFTNGP05.phx.gbl...
Ace Fekay [MCT]
> Hi! Ace,
> These DC are internal domain controllers. We cannot access internet from
> these boxes.
> I will go thru the url you provided and update you. Appreciate your help!.
>
> Hugo
Hi Hugo,
I understand they are internal DCs, however because the servers are DNS
servers, they will need access for forwarders (if you setup forwarders as
recommended), and/or queries to the Root hints.
Let me know what you find.
Ace