Problem w/ 8.2.1 ( was: possible problem w/ 8.2.1)

bas aerts bas_aerts at ins.com
Fri Jul 2 15:10:06 UTC 1999


But like I have so many of them (like 174 within 24 hours).
for a moderately used name server. Is this normal then?






-----Original Message-----
From: Jim Reid [mailto:jim at mpn.cp.philips.com]
Sent: Friday, July 02, 1999 3:01 PM
To: bas_aerts at ins.com
Cc: Bind Users Mailing List
Subject: Re: Problem w/ 8.2.1 ( was: possible problem w/ 8.2.1)


>>>>> "bas" == bas aerts <bas_aerts at ins.com> writes:

    bas> I also have this problem with the 'lame' servers and stuff:

No, you have a different problem from the one that Kevin Martin
reported.

    bas> Jul 1 17:37:47 amsftp00 named[2572]: Response from unexpected
source ([194.178.56.6].53)

Your name server got a reply from an IP address (194.178.56.6) that it
hadn't anticipated would send a reply. Your server made a query to one
IP address, but the response came back from a different one. Maybe the
server that was queried has >1 network interface or maybe someone is
trying to poison your name server by faking replies.

    bas> Jul 1 17:38:07 amsftp00 named[2572]: Lame server on 'ugc.com' (in
'ugc.com'?): [198.62.195.99].53 'PEGASUS.CVG-GRP.COM'

Your name server tried to get an authoritative answer for the ugc.com
from the name server at 198.62.195.99 and it gave a non-authoritative
reply. So that remote name server is broken or else the NS records for
ugc.com point at the wrong name servers. This is known as a lame
delegation. It's a depressingly common problem on the
Internet. There's nothing you can do about this apart from contact the
DNS admin for ugc.com and tell them they have a lame delegation.

    bas> Jul 1 17:38:12 amsftp00 named[2572]: ns_forw: query(ugc.com) All
possible A RR' s lame

All the name servers listed for ugc.com are not giving authoritative
answers for that domain. The DNS admin for ugc.com has screwed up big
time.



More information about the bind-users mailing list