Re: named complaining about lame servers when resolving

[Arnt Karlsen <arnt@c2i.net>]

On Wed, 24 Sep 2003 00:56:18 -0600, 
bob@proulx.com (Bob Proulx) wrote in message 
<[🔎] 20030924065618.GB9219@misery.proulx.com>:

> Malcolm Ferguson wrote:
> > Jacob Anawalt wrote:
> > > Malcolm Ferguson wrote:
> > > > Error message (repeated over and over):
> > > > Sep 22 17:12:00 ns1 named[12680]: lame server resolving 
> > > > '75.1.5.198.in-addr.arpa' (in '1.5.198.in-addr.arpa'?):
> > > > 198.6.1.161#53
> > >
> > >Are you recieving SMTP or other external traffic with a service
> > >that may be trying to resolve IP addresses to names?

..<snip>.
 
> I looked up that address and I also see the lame server on my end.  It
> appears that auth03.ns.UU.NET and auth50.ns.UU.NET are designated as
> authoritative for 1.5.198.in-addr.arpa but that they are not
> configured to return answers for 75.1.5.198.in-addr.arpa which they
> should since it is within their domain.  In fact the two servers
> return completely different data to queries.  In DNS speak, they are
> 'lame'.  In the vernacular, they are hosed up.
> 
> Here are commands which should return the same information but show
> some of the problems.  The first shows that the second two are
> supposed to be the authoritative name servers.  If I read this right I
> would say they are b0rken.
> 
>   dig 1.5.198.in-addr.arpa ns
>   dig @auth03.ns.UU.NET 75.1.5.198.in-addr.arpa ptr
>   dig @auth50.ns.UU.NET 75.1.5.198.in-addr.arpa ptr

..any chance one of these boxes is cracked?

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.