DNS Error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The DNS server encountered a packet addressed to itself on IP address
192.168.1.100. The packet is for the DNS name
"2b1ce964-44de-49b0-8c27-f351d9714d9c._msdcs.mydomain.local.". The packet
will be discarded. This condition usually indicates a configuration error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server.
5) Root hints.

Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone
example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of
bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.

Note, you should make this delegation check (with nslookup or DNS manager)
both on this DNS server and on the server(s) you delegated the subzone to. It
is possible that the delegation was done correctly, but that the primary DNS
for the subzone, has any incorrect NS record pointing back at this server. If
this incorrect NS record is cached at this server, then the self-send could
result. If found, the subzone DNS server admin should remove the offending
NS record.

You can use the DNS server debug logging facility to track down the cause of
this problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
 
In
Stormin said:
The DNS server encountered a packet addressed to itself on IP address
192.168.1.100. The packet is for the DNS name
"2b1ce964-44de-49b0-8c27-f351d9714d9c._msdcs.mydomain.local.". The
packet will be discarded. This condition usually indicates a
configuration error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server.
5) Root hints.

Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the
zone example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of
bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.

Note, you should make this delegation check (with nslookup or DNS
manager) both on this DNS server and on the server(s) you delegated
the subzone to. It is possible that the delegation was done
correctly, but that the primary DNS for the subzone, has any
incorrect NS record pointing back at this server. If this incorrect
NS record is cached at this server, then the self-send could result.
If found, the subzone DNS server admin should remove the offending NS
record.

You can use the DNS server debug logging facility to track down the
cause of this problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Click to expand...

Do you have a forwarder configured? That usually eliminates this error.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
I have a forwarder set up to point to my ISP's DNS servers. Isn't this
required for me to be able to get Internet access? Please advise.

"Ace Fekay [MVP]"
 
In
Stormin said:
I have a forwarder set up to point to my ISP's DNS servers. Isn't
this required for me to be able to get Internet access? Please
advise.
Click to expand...

It's not necessarily "required", rather recommended. Does your ISP's DNS
allow forwarding? You can test it with nslookup -d2, or can download NetDig
from www.mvptools.com. Run a query using your ISP's DNS. If it supports it,
you will see an RD and RA response (recurision desired, recursion
available). If it doesn't, you will just see the RD.

One more thing, since we do not have any config info, we're in guessing mode
here. Can you provide more info? I previously asked 'stopnowgo' for
additional info. I do not know if "Stormin" is the same person or not, but
the additional info would still apply.

Ace
 
Back
Top