OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
SP4 & DNS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SP4 & DNS

  • To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
  • Subject: SP4 & DNS
  • From: "Info, Kamar" <infoKAMAR.COM>
  • Date: Fri, 4 Dec 1998 16:16:55 +0100
  • Approved-By: Russ.CooperRC.ON.CA
  • Reply-To: "Info, Kamar" <infoKAMAR.COM>
  • Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>
Hi there,
Been running NT4.0 SP3 for more than a year almost without problems, but
after installing SP4 the eventlog is creating almost every half hour an
error event 7062 with the hereunder mentioned problem. We run primary DNS
for ourselves and our ISP (who runs secundary) demands an A-record for our
NS (ns.ourcompany.com).
If I remove this record no problems in the eventlog, but my ISP is calling
within an hour why they cannot resolve ns.mycompany.com anymore.
Dos anyone know what to do?
Thanks in advance,
Arno Hendrikx
infokamar.com
----------------------------------------------------------------------------
------------
Event 7062
DNS Server encountered a packet addressed to itself -- IP address
"100.100.100.100". 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.