My bind server is freaking out.  It just started this afternoon, when I
noticed absurd amounts of errors in my syslog like these:

syslog:Feb 27 16:41:03 rome named[476]: lame server resolving
'CROSSROADSCONCERTS.net' (in 'CROSSROADSCONCERTS.NET'?):
216.147.43.234#53
syslog:Feb 27 16:41:04 rome named[476]: lame server resolving
'CROSSROADSCONCERTS.net' (in 'CROSSROADSCONCERTS.NET'?):
216.147.1.164#53
syslog:Feb 27 16:41:16 rome named[476]: lame server resolving
'CROSSWIND-CAFE.net' (in 'CROSSWIND-CAFE.NET'?): 210.157.0.1#53
syslog:Feb 27 16:41:16 rome named[476]: lame server resolving
'CROSSWIND-CAFE.net' (in 'CROSSWIND-CAFE.NET'?): 210.157.0.2#53

When I looked up the error, I found that this error means that the DNS
server being queried (not my box, but the IP addresses at the end of the
lines) is not authoritative for the domain name being looked up. 
However, nobody (that I know of) is making queries from my machine.  I
even ran tcpdump with the name port to see if anything was coming in or
going out on any interface (including lo), and I didn't see any traffic,
yet named was still getting processor time, and new entries were forming
in my syslog.  I tried restarting bind, but with the same results.  Any
ideas as to what is going on?

Casey


____________________
BYU Unix Users Group 
http://uug.byu.edu/ 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to