Re: how to reduce traffic caused by lame delegation

In article <bdv853$190f$1@sf1.isc.org>, Wolf-D. Perl <perl@smk-gmbh.de> wrote:
>Jul 2 13:27:31 server named[4810]: lame server resolving
>'34.254.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
>198.116.144.33#53

I queried that server, and it doesn't seem to be lame.

128.102.x.x is an address block used by NASA Ames Research Center. Do you
have any regular dealings with them that might be the reason why you're
looking up their addresses so much?

It's also strange that the query logging doesn't show any queries coming in
for x.x.102.128.in-addr.arpa.

>Jul 2 13:27:31 server named[4810]: lame server resolving
>'5.78.159.64.in-addr.arpa' (in '78.159.64.in-addr.arpa'?):
>64.159.80.3#53

This server is indeed lame. And here's a log message showing one of your
internal systems trying to look it up:

>Jul 2 13:27:33 server named[4811]: client internal_ip#52744: query:
>5.78.159.64.in-addr.arpa IN PTR

--
Barry Margolin, barry.margolin@level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.