I am getting the following warning in my DNS event log. The server is win2000, it has two nics one for global ip and other for local ip and my corporte website is hosted on that.
I am not able to connect to any cleint from my server and vice versa. I am screwed up, please help me. Any more information required, please intimate.
The error is:
DNS Server encountered a packet addresses to itself -- IP address <ip address>. 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 server 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 DNS server
Example: -> This DNS server dns1.microsoft.com is the primary for the zone microsoft.com. -> You have delegated the zone bar.microsoft.com to bardns.bar.microsoft.com and are NOT running the bar.microsoft.com zone on this DNS (dns1.microsoft.com). Note, you should make this check (with nslookup of 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.
regards,
Dblaine
I am not able to connect to any cleint from my server and vice versa. I am screwed up, please help me. Any more information required, please intimate.
The error is:
DNS Server encountered a packet addresses to itself -- IP address <ip address>. 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 server 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 DNS server
Example: -> This DNS server dns1.microsoft.com is the primary for the zone microsoft.com. -> You have delegated the zone bar.microsoft.com to bardns.bar.microsoft.com and are NOT running the bar.microsoft.com zone on this DNS (dns1.microsoft.com). Note, you should make this check (with nslookup of 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.
regards,
Dblaine