Strange slave DNS errors *SOLVED*

[Kirk Hoganson]

For archival purposes I would like to indicate the solution here. 
Thanks to everyone who responded about this problem.  It turned out to 
be a local configuration problem.  Someone had modified the interfaces 
configuration file and caused the lo interface not to load properly. 
Fixing the file cleared up this problem.

Mark Andrews said the following:
>>I found some reference to similar problems in the archives.  However the 
>>suggested solution of upgrading has not fixed the problem.  I am now 
>>running 9.3.1, and the problem persists exactly as before.  My logs are 
>>filling up with these errors:
>>
>>Aug 19 11:01:41 ns2.domain.com named[162]: socket.c:1115: unexpected error:
>>Aug 19 11:01:41 ns2.domain.com named[162]: internal_send: 66.7.6.158#53: 
>>Invalid argument
>>Aug 19 11:17:26 ns2.domain.com named[162]: socket.c:1115: unexpected error:
>>Aug 19 11:17:27 ns2.domain.com named[162]: internal_send: 66.7.6.158#53: 
>>Invalid argument
> 
> 
> 	Linux will return "Invalid argument" when the firewall drops
> 	a packet.  Why they had to overload this error code I will
> 	never know.
>  
> 	Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org