Im still kind of a newbie at dns... Wonder if you can help me figure this out? I keep getting hundreds of yellow alerts in my dns event viewer log. EventID 7062. Also getting eventid 9999. At the very bottom of my post is a sample of my zone files. Can you spot anything that im doing wrong?
Basically i have a VERY simple configuration. Ive only got 1 NT server which hosts my Dns also. In my zone file its set as NS1.MyHostingCompany.com and NS2.MyHostingCompany.com this is pointed my web server. So when I register any new domains I use the ns1. and ns2. addresses.
What am I doing wrong??? Thanks!
-Matt
**************Text for ID 9999**********************
The DNS server has encountered numerous run-time events. These are usually caused by the reception of bad or unexpected packets, or from problems with or excessive replication traffic. The data is the number of suppressed events encountered in the last 15 minute interval.
**************Text for ID 9999**********************
**************Text for ID 7062**********************
The DNS server encountered a packet addressed to itself -- IP address 21.96.63.27.
The DNS server should never be sending a packet to itself. This situation 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.
Example of self-delegation:
-> This DNS server dns1.foo.com is the primary for the zone foo.com.
-> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com,
(bar.foo.com NS dns1.foo.com)
-> BUT the bar.foo.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.
**************Text for ID 7062**********************
**************SAMPLE Zone file im getting errors with**********************
;
; Database file MyDomain.com.dns for MyDomain.com zone.
; Zone version: 2003111903
;
@ IN SOA ns1.MyHostingCompany.com. admin.MyDomain.com. (
2003111903 ; serial number
3600 ; refresh
600 ; retry
1209600 ; expire
3600 ) ; minimum TTL
;
; Zone NS records
;
@ NS ns1.MyHostingCompany.com.
ns1.MyHostingCompany.com. A 21.96.63.26
@ NS ns2.MyHostingCompany.com.
ns2.MyHostingCompany.com. A 21.96.63.27
;
; Zone records
;
@ A 21.96.63.26
@ MX 10 mail.MyDomain.com.
ftp A 21.96.63.26
mail A 21.96.61.187
www A 21.96.63.26
**************SAMPLE Zone file im getting errors with**********************
