4010 Error continue

  • Thread starter Thread starter Reed Wiedower
  • Start date Start date
R

Reed Wiedower

I've been having this issue for about two weeks now: each time I restart
either of my two DNS servers the logs are filled with 4010 errors that point
back to my NAT-addressed internal ip scheme:

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4010
Date: 5/17/2004
Time: 3:11:01 PM
User: N/A
Computer: DNSSERVERONE
Description:
The DNS server was unable to load a resource record (RR) from the directory
at 21.0.168.192.in-addr.arpa. in zone 168.192.in-addr.arpa. Use the DNS
console to recreate this RR or check that the Active Directory is
functioning properly and reload the zone. The event data contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 00 00 00 {...


Each of the machines in the 192.168.0.x zone generates an error like this
one when either of the two DNS servers attempts to reload the zone. In an
attempt to try and solve the problem, I've deleted the zone and recreated
it, to no avail. I've also reregistered the network adapters on both servers
and flushed the cache multiple times. Any other ideas?

end of line,

Reed Wiedower
 
In
Reed Wiedower said:
I've been having this issue for about two weeks now: each time I
restart either of my two DNS servers the logs are filled with 4010
errors that point back to my NAT-addressed internal ip scheme:

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4010
Date: 5/17/2004
Time: 3:11:01 PM
User: N/A
Computer: DNSSERVERONE
Description:
The DNS server was unable to load a resource record (RR) from the
directory at 21.0.168.192.in-addr.arpa. in zone 168.192.in-addr.arpa.
Use the DNS console to recreate this RR or check that the Active
Directory is functioning properly and reload the zone. The event data
contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 00 00 00 {...


Each of the machines in the 192.168.0.x zone generates an error like
this one when either of the two DNS servers attempts to reload the
zone. In an attempt to try and solve the problem, I've deleted the
zone and recreated it, to no avail. I've also reregistered the
network adapters on both servers and flushed the cache multiple
times. Any other ideas?

end of line,

Reed Wiedower
Click to expand...


In a situation like this, sometimes it's easier to just delete the zone and
re-create it. I would first delete the netlogon.dns file, and restart the
netlogon service to see if it goes away. Here;'s more info:

http://www.eventid.net/display.asp?eventid=4010&eventno=791&source=DNS&phase=1

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
In
Reed Wiedower said:
Thanks...that nailed it.

eol,

Reed
Click to expand...



Glad it helped!
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top