[NTLUG:Discuss] Should I be concerned? Error from named

[brad angelcyk]

Have you tried using a packet sniffer on port 53 to
see where the packets are originating from and what
they are?

Also, set the debugging level to 3 for more detail on
the error.  (-d3 when you start named)

Brad


--- Jay Urish <j at unixwolf.net> wrote:
> Hey gang,
> I have seen this on 2 different servers now...
> Should I be concerned? Its 
> showing up on my server AND a customers server...
> Feb 13 09:01:01 mail CROND[31887]: (mail) CMD
> (/usr/bin/python -S 
> /var/lib/mailman/cron/qrunner)
> Feb 13 09:01:40 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:40 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> Feb 13 09:01:42 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:42 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> Feb 13 09:01:44 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:44 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> Feb 13 09:01:50 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:50 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> Feb 13 09:01:52 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:52 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> Feb 13 09:01:52 mail named[20709]: socket.c:1100:
> unexpected error:
> Feb 13 09:01:52 mail named[20709]: internal_send:
> 244.254.254.254#53: 
> Invalid argument
> 
> It looks scary... WTF?
> 
> 
> Jay Urish       W5GM            Systems/Network
> Engineer
> Unixwolf Enterprises    972.691.0125    972.965.6229
> 
> http://www.unixwolf.net         AIM:jayurish 
> 
> 
> 
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss


__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html