RE: [IMail Forum] Off Topic: DNS

[Dan Shadix]

Item 1)  Open DNS Manager, select the server name, select Properties from the DNS menu.  Under the forwarders tab see if you have listed the server's own IP address.  If yes, remove it.

 

Item 2) & 3)  Select each zone and view it's properties.  If it is a primary zone look under the Notify tab for the server's IP.  Remove it if it's there.  If it is a secondary zone, look on the General tab under Secondary IP masters.  If you find the server's IP remove it.

 

Item 4)  I hope it's not this one because I don't have time to explain it and probably wouldn't do a very good job anyway.  If your domain were domain.com and you have other domains like sub.domain.com so that a computer might be named computer.sub.domain.com this might be the problem.  Otherwise it isn't.

Dan Shadix
Computer Network Manager
Terry Reilly Health Services

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Graveen
Sent: Thursday, April 06, 2000 1:04 PM
To: [EMAIL PROTECTED]
Subject: [IMail Forum] Off Topic: DNS

I know this is an off topic question, but I figure with the amount of people familiar with DNS on this list, this was the best place to start.

I've been getting this repeated error message in the Event Viewer:

2/17/00 8:44:27 PM Dns Error None 7062 N/A NS
DNS Server encountered a packet addressed to itself -- IP address 63.225.64.50. 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 DNS server      Example:     -> This DNS server dns1.foo.com is the primary for the zone foo.com.     -> You have delegated the zone bar.foo.com to bardns.bar.foo.com. and         are NOT running the bar.foo.com zone on this DNS (dns1.foo.com).     -> bar.foo.com MUST NOT have an NS record that points at dns1.foo.com.      Note, you should make this 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.
******************************************************************************************************

I am running Windows NT server 4.0 Service Pack 4, Microsoft DNS. I thought I had configured the DNS correctly but I am not sure what I did wrong.  If any one can tell by the error message what I am doing wrong I would greatly appreciate it.  Thanks in advance.

Michael Graveen Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list.