Not sure what has happenned here I left this list 12 months ago and
I am now suddenly back on it.
Something has gone wrong, perhaps the list owner could post instructions?
Gordon
At 11:00 14/11/98 -0600 Josh Dowdell said....
>HOW DO YOU GET OFF THIS THIS LIST????
>
>Josh Dowdell -- Josh@Dowdell.com -- Dallas, TX USA
>972-663-4020 -- FAX: 972-663-4010 -- http://www.dowdell.com
>-- Allaire Alliance Partner and Builder of Interactive web sites --
>
>
>
>> -----Original Message-----
>> From: ntisp-request@iea-software.com
>> [mailto:ntisp-request@iea-software.com]On Behalf Of Adam Greene
>> Sent: Saturday, November 14, 1998 9:21 AM
>> To:
>> Subject: Re: MS DNS Error
>>
>>
>> Hi, Paul,
>>
>> To be honest, I don't know too much about this myself, but
>>
>> I would suggest going into DNS Manager. If you right-click on any primary
>> zone you have there, and select the Notify tab, you will see if
>> that zone is
>> trying to send information somewhere.
>>
>> If you comb your zones (examine all of the records for each zone) you may
>> find that some zone is for some reason trying to send information
>> to itself.
>>
>> I'm not sure if that's the problem, but the "fine-toothed comb"
>> approach has
>> worked for me in the past.
>>
>> Good luck,
>> Adam
>> -----Original Message-----
>> From: Paul T Laudenslager <ptl@monumental.com>
>> To: ntisp@iea-software.com <ntisp@iea-software.com>
>> Date: Friday, November 13, 1998 3:29 PM
>> Subject: MS DNS Error
>>
>>
>> >I'm having an error show up in the event viewer regarding my DNS
>> server. I
>> >have my domain, "virginia.com", as well as approx 32 others
>> (most of which
>> >are on a shared ip of 4.21.72.140) running on a NT4AS-sp4
>> system. I setup
>> >all of my customers pretty much the same way and I've been
>> unable to track
>> >down the error. You may use nslookup, but I'm not sure where to look to
>> >find the error.
>> >
>> >Thanks in advance for your time and consideration.
>> >Paul & Susan Laudenslager
>> >paul@virginia.com
>> >susan@virginia.com
>> >
>> >The error is as follows...
>> >
>> >DNS Server encountered a packet addressed to itself -- IP address
>> >4.21.72.130.
>> >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.
>> >
>> >
>> >
>>
>>
>
>