Fwd: Strange 9.6.0-P1 issue

2009-03-19 Thread c0re dumped
> You need to provide actual DNS names and IP addresses, otherwise we > won't be able to help you. 19-Mar-2009 08:37:07.130 no valid RRSIG resolving 'www.estadao.com.br/A/IN': 200.185.6.131#53 19-Mar-2009 08:37:07.147 no valid RRSIG resolving 'www.estadao.com.br/A/IN': 200.185.6.163#53 19-Mar-2009

Re: Strange 9.6.0-P1 issue

2009-03-17 Thread c0re dumped
Just forgot: I'm using dnssec 2009/3/17 c0re dumped : > I don't what could it be, but I'm getting tons of > > "no valid RRSIG resolving 'www.xyz.xom/A/IN': X.X.X.X.#53" > > messages > > > -- > http://setsockopt.word

Re: Strange 9.6.0-P1 issue

2009-03-17 Thread c0re dumped
I don't what could it be, but I'm getting tons of "no valid RRSIG resolving 'www.xyz.xom/A/IN': X.X.X.X.#53" messages -- http://setsockopt.wordpress.com http://www.webcrunchers.com/crunch ___ bind-users mailing list bind-users@lists.isc.org https://

Strange 9.6.0-P1 issue

2009-03-17 Thread c0re dumped
Hello guys, I recently upgraded my bind to the 9.6.0-P1 version, since then my nameserver hangs everyday at night. The only names I can resolv, are the cached ones. The machine: - FreeBSD 7.1 - Bind 9.6.0-P1 (installed from ports) - named flags: BIND 9.6.0-P1 built with '--localstatedir=/var' '