If I remember correctly, I think that is a known bug with the NT DNS service
(Service Pack 5). I had that problem myself some time ago. What service
pack are you running? I don't have my knowledge base info available, but I
think you should be able to find it via Microsoft's TechNet web site.
Jeff
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of George Laiacona
III
Sent: Monday, May 01, 2000 4:18 PM
To: [EMAIL PROTECTED]
Subject: DNS Configuration, possible loop?
Fellows:
I had asked this earlier, and was getting some progress, but as yet had not
resolved the problem.
I get an error message from my NT server, which acts as the domain slave:
"DNS Server encountered a packet addressed to itself -- IP address
216.77.135.35. 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. "
Now, I have looked over my files, and as best as I can tell, they are
correct. But there's more. After a time, these errors get real repetitive in
the event viewer in NT. Mail, handled by the same machine as my Master
Nameserver, gets real slow.
After a restart of the nameserver, a RedHat 6 box, the problems go away for
a few hours, or days, but come back.
Is it possible to get a little help from the list? Has anyone gone through
this either? A few clues at least!
Thanks immensely.
George Laiacona III <[EMAIL PROTECTED]> ICQ 37042478/ 28885038
"You can kill some of the people all of the time, and you can kill all of
the people some of the time, but you can't kill all of the people all of the
time...because then who'll grow the food?"
-Excerpts, King's Men Political Manual
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
