Rndc reload hang

Hello, we are using in a production environment Bind-9.10.1 Since i install it, i had sometimes problems with dns resolution By typing "rndc reload" the system seems in "hung": i have named process running, but i cannot have any dns resolution and i cannot kill the named process with -INT or -H

NSEC3 wildcard validation failures [was: Wrong NSEC3 for wildcard cname]

Hi Folks, I think we can wrap this up thanks to assistance from the reporting site - they're running BIND 9.8.1-P1 (stock package in Ubuntu 12.04 LTS). This means they don't have the following fix, which appeared in 9.8.2b1. 3175. [bug] Fix how DNSSEC positive wildcard responses fro

Re: Wrong NSEC3 for wildcard cname

On Wed, Nov 19, 2014 at 7:03 PM, Graham Clinch wrote: > Thanks - that's certainly looking less red. DNSViz is an exceptionally > useful tool! > > Thanks! > ... > > delv +vtrace continues to report "NSEC3 at super-domain" only for > foo.cnametest2.palatine.ac.uk records, and not for > foo.cname

Slow check for named-checkconf

Hello, i am use BIND version 9.9.5. DNS records stored in files. Fast load zones released in startup by enabling zones to load in multiple threads. ( [RT #25333] ) But named-checkconf work too slow. Somebody, use check local files, before reloading BIND configuration? For checking zone files