Warning 7062...

Warning 7062...

Post by ivanj » Sat, 14 Jan 2006 01:00:18


We have a Win 2003 Server , our network have only 1 server (192.168.2.250)
and in the DNS event viewer I get this "warning" like 180 times per day :

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
The DNS server encountered a packet addressed to itself on IP address
192.168.2.250.
The packet is for the DNS name
"_ldap._tcp.Default-First-Site._sites.gc._msdcs.TallerBorinquen.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://www.yqcomputer.com/ "
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
first,
how I remove ther server from the "Forwarders list"
any help would be appreciated

ivan
 
 
 

Warning 7062...

Post by Kevin D. G » Sat, 14 Jan 2006 02:14:45


This is more likely a delegation in place when there is no
_msdcs.TallerBorinquen.local forweard lookup zone on the servers listed in
the _msdcs delegation within the TallerBorinquen.local forward lookup zone.

Check the NS records listed in the delegation to make sure all DNS servers
with NS records have the _msdcs.TallerBorinquen.local zone. It could be that
there is a server with an NS record in the delegation does not have this
zone, but that server forwards to this one.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.yqcomputer.com/
http://www.yqcomputer.com/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://www.yqcomputer.com/ ~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.yqcomputer.com/
===================================