![nanog logo](/images/nanog-logo.png)
nanog mailing list archives
Re: Interesting BIND error
From: Crist Clark <crist.clark () globalstar com>
Date: Thu, 12 Feb 2004 14:59:40 -0800
Brian Bruns wrote:
On Thu, February 12, 2004 4:52 pm, Brian Wallingford said:We've been seeing the following on all of our (9.2.1) authoritative nameservers since approximately 10am today. Googling has turned up nothing; I'm currently trying to glean some useful netflow data. Just wondering if this is local, or if others have suddenly seen the same. Seems harmless enough, but the logging is eating a disproportionate amount of cpu. Feb 12 16:25:07 ns1 named[3150]: internal_send: 244.254.254.254#53: Invalid argumentIts possible that someone is spoofing UDP packets to your nameserver from that IP range (which is IANA reserved space).
That's the old Class E space. Definately not routed over the Internet. > It looks like BIND is
refusing to send to that address, and thus the error.
Or the OS is. -- Crist J. Clark crist.clark () globalstar com Globalstar Communications (408) 933-4387
Current thread:
- Interesting BIND error Brian Wallingford (Feb 12)
- Re: Interesting BIND error Chris Adams (Feb 12)
- Re: Interesting BIND error jlewis (Feb 12)
- Re: Interesting BIND error Brian Bruns (Feb 12)
- Re: Interesting BIND error Vinny Abello (Feb 12)
- Re: Interesting BIND error Matthew Sullivan (Feb 12)
- Re: Interesting BIND error Valdis . Kletnieks (Feb 12)
- Re: Interesting BIND error Matthew Sullivan (Feb 12)
- Re: Interesting BIND error Crist Clark (Feb 12)
- Re: Interesting BIND error Chris Adams (Feb 12)
- Re: Interesting BIND error Joe Abley (Feb 12)
- Re: Interesting BIND error Mike Lewinski (Feb 12)
- Re: Interesting BIND error Valdis . Kletnieks (Feb 12)