OT: nameservers went lame

[Mark Nienberg]

I'm running a cacheing-only nameserver on my MailScanner server.  It was quiet for
months, but now I see lots of these in the logs:

Jul 27 12:40:03 gingham named[3316]:
lame server resolving '19.160.99.61.in-addr.arpa'
(in '160.99.61.in-addr.arpa'?): 210.117.65.2#53

Is there something wrong at the root level nameservers?  Perhaps I need a new
version of the "named.conf" file?  Anybody else seeing this?  That said, everything
still works fine.  Names are being resolved, RBL's and SURBL are working.

To be fair, this started a few days ago after I did a kernel update and rebooted, but
that seems like a coincidence.  Thanks for any insight and I apologize for asking this
here, but you folks seem to know everything!
--
Mark W. Nienberg, SE
Tipping Mar + associates
1906 Shattuck Ave, Berkeley, CA  94704
visit our website at http://www.tippingmar.com

-------------------------- MailScanner list ----------------------
To leave, send    leave mailscanner    to jiscmail at jiscmail.ac.uk
Before posting, please see the Most Asked Questions at
http://www.mailscanner.biz/maq/     and the archives at
http://www.jiscmail.ac.uk/lists/mailscanner.html