EVENT ID 7062

  • Thread starter Thread starter CasDeTroy
  • Start date Start date
C

CasDeTroy

I am getting this in my dns log:

The DNS server encountered a packet addressed to itself --
The DNS server should never be sending a packet to
itself.

What is happening?

Please help.
THx
 
Do you have a forwarder configured?

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Also to add, does this server have mutliple NICs? Can you also post an
unedited ipconfig /all to get a better idea of your configuration?
Thanks

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
CasDeTroy said:
I am getting this in my dns log:

The DNS server encountered a packet addressed to itself --
The DNS server should never be sending a packet to
itself.

What is happening?

Please help.
THx
Click to expand...

It is either forwarding to itself, try to do a zone transfer to itself, or
it has a delegation pointing to itself for a name it does not have.

what are its forwarders?
how are the zone transfers set up?
Is the a delegation in one of its zones, say for a child domain, when the
child zone does dot exist?
 
i have actually got a primary dns which is running on the
dc and a sec dnd running on a bdc. Forwarders are not
configured.

If i need to config forwarders they would be pointing to
them selves as they are active dir. intergrated.

There are no child domains on my network (there used to be
one but is no more).

Can you please get me the solution from this info?
 
See below inline please for my responses...

CasDeTroy said:
i have actually got a primary dns which is running on the
dc and a sec dnd running on a bdc. Forwarders are not
configured.
Click to expand...

I don't understand your terminology of a "BDC" here. Do you mean the
secondary zone is running on an NT4 BDC? I ask because the PDC/BDC
terminology does NOT apply to W2k or W2k3 machines. It's legacy.

So do you mean that you have a zone that is AD Integrated on one DC and you
have the same zone on another DC that is also AD Integrated?
OR do you mean that you have a Primary zone on one server (not nevcessarily
a DC) and you have a Secondary zone on another machine, that is a Seconary
zone (not AD Integ or Primary zone) possible another W2k DC?

Please elaborate.
If i need to config forwarders they would be pointing to
them selves as they are active dir. intergrated.
Click to expand...

A forwarder is actually a setting that you would setup on your DNS server so
that if it receives a query for an unknown name, it will "Forward" the
request to an external DNS, such as your ISP's. In the case of a forwarder,
never forward to a partner DNS that has the same exact zone information on
it or you'll lock it in a forwarding loop.

The only time you would forward to another within an organization is with
the use of child domains and delegation, but this does not apply to you
here.

AD Integrated just means that the zone information is stored in the AD
database instead of as a text file in system32\dns folder. It's secure in
the AD database. IT also gets replicated to other DCs in teh same domain
because of AD replication. That;'s why it's easy to install DNS on another
machine and create the zone then make it AD Itegrated and the zone data
magically pops up.

AD Integrated zones have NOTHING to do with Forwarding.
 
I had this error crop up recently. I found that the server in question had
an additional, erroneous, IP address, bound to its primary adapter. It
registered both IP addresses, one in each subnet, with DNS. Apperently this
caused the server to querry itself in an attempt to resolve the bad address.
I removed the address and flushed the DNS cache and things started working
correctly.
-mats
 
In
CasDetroy said:
I have a zone that is AD Integrated on one DC and you
have the same zone on another DC that is also AD
Integrated
Click to expand...
I see. So they are not Primary/Secondary as your original post said. That
clears it up a bit.

If this is so, try to arrange the DNS entries in the two DCs' IP properties
like this:

DC1:
1st entry: DC2' IP
2nd entry: DC1's IP

DC2:
1st entry: DC1's IP
2nd entry: DC2's IP




--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
This happens if the DNS server receives a referal for a DNS lookup that refers the DNS server to itself. For instance, supose
you have a zone configured on your DNS server and this zone is registered on the Internet. You decide to delete this zone on
the server without updating the registrar about the change. Some client on your network makes a query for a record in this zone.
In the process of trying to resolve this record, the DNS server will get refered to itself as a name server for this record. At that
point it queries itself and you get this error. There are a number of scenarios that can cause this behavior. If you enable DNS
logging on the DNS server, wait for this error to pop up, and then check the logs, it will show you exactly the query that caused
the error. You can then track down and fix exactly what caused it in your case.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Back
Top