On Feb 13, 2007, at 11:14 PM, Andy Smith wrote:
On Tue, Feb 13, 2007 at 10:17:49AM -0500, Rich Johnson wrote:
What is surprising is that such an event brought down _another_
machine.
Would it be fair to say that excessive loggers are ill-behaved?
It sounds like your bind was
On 12.02.07 09:55, Rich Johnson wrote:
I just recovered from bind (8.4.7-1) flooding /var/log/syslog with
several hundred megabytes of messages along the lines of:
grep no addrs found for root syslog | head
Feb 10 19:54:59 creaky named[7652]: sysquery: no addrs found for root
NS
On Feb 13, 2007, at 3:12 AM, Matus UHLAR - fantomas wrote:
On 12.02.07 09:55, Rich Johnson wrote:
well, i suggest you
- upgrade to bind9 (preferrably 9.3)
- check your named.root zone, if it exists and if you have it
configured.
Done! Let's hope it helps. I run dist-upgrade (testing)
On Tue, Feb 13, 2007 at 10:17:49AM -0500, Rich Johnson wrote:
What is surprising is that such an event brought down _another_ machine.
Would it be fair to say that excessive loggers are ill-behaved?
It sounds like your bind was misconfigured and didn't know what the
IPs of the root servers
OUCH!
I just recovered from bind (8.4.7-1) flooding /var/log/syslog with
several hundred megabytes of messages along the lines of:
grep no addrs found for root syslog | head
Feb 10 19:54:59 creaky named[7652]: sysquery: no addrs found for root
NS (B.GTLD-SERVERS.net)
Feb 10 19:54:59
5 matches
Mail list logo