DNS Error Event 7062
Hi,
I look after a simple Windows 2003 server setup with 5 clients. However I am getting lots of event 7062 errors:
"The DNS server encountered a packet addressed to itself on IP address 192.168.0.20. The packet is for the DNS name "_ldap._tcp.a2700020-cc38-
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
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com
(bar.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."
I have looked on EE and around the internet and I find a Microsoft Support document that lists how to fix it. The problem with it is that it refers to Windows 2000 and NT 4.0 so some of the fixes it suggests aren't there.
Any help greatly appreciated.
Mike
I look after a simple Windows 2003 server setup with 5 clients. However I am getting lots of event 7062 errors:
"The DNS server encountered a packet addressed to itself on IP address 192.168.0.20. The packet is for the DNS name "_ldap._tcp.a2700020-cc38-
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
-> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com
(bar.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."
I have looked on EE and around the internet and I find a Microsoft Support document that lists how to fix it. The problem with it is that it refers to Windows 2000 and NT 4.0 so some of the fixes it suggests aren't there.
Any help greatly appreciated.
Mike
ASKER
Hi,
This may seem like a dumb question but how do you find the IP for my ISP's DNS. I assume it will be in the router configuration?
Mike
This may seem like a dumb question but how do you find the IP for my ISP's DNS. I assume it will be in the router configuration?
Mike
Hi,
I guess you'll have to phone them. They should've supplied it to you when you applied for their services.
Cheers
I guess you'll have to phone them. They should've supplied it to you when you applied for their services.
Cheers
ASKER
hi,
I have found this out and put it into the forwarders lists. I then stopped and restarted the DNS Client and DNS Server services. However I am still getting the event 7062.
Mike
I have found this out and put it into the forwarders lists. I then stopped and restarted the DNS Client and DNS Server services. However I am still getting the event 7062.
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for that - reinstall seemed to work.
Have you tried:
The TCP/IP settings for your SBS server's NIC should point to its own address for DNS resolution. In your DNS server settings, you should have a forwarder configured to point to your ISP's DNS servers.
To set up a forwarder, open the DNS console, right-click your server, and select Properties. Go to the Forwarders tab, highlight "All other DNS domains" and add your ISP's DNS server address(es). This way, your server will handle DNS queries for your domain but will forward everything else to your ISP.
Also, make sure your domain's DNS name doesn't match a valid Internet domain name. Otherwise, you could have some strange occurrences. (Usually that'll just render that Internet domain inaccessible from your network.
Let me know!
Cheers