Which timeouts are used by BIND when resolving recursive queries?

Hi, I understand that I can configure a global timeout for resolving recursive queries (resolver-query-timeout) but find that I cannot configure the timeout for an individual query used during DNS resolution. For testing I configured one unreachable forwarder (and enabled forward only) and saw

Unexpected wildcard matching

Hello, I want to have a dummy (internal) root NS to resolve specific name hello.test.com to 4.5.6.7, everything else to 1.2.3.4. Using a wildcard does not work as expected (by me), though. 1st attempt: # cat db.root $TTL 86400 @ IN SOA ns1.root.internal. dnsadmin.

global forwarders - current BIND9 behaviour documentation

Hi, anybody there who can provide a definitive answer on the current BIND 9.7 (or higher) global forwarder behaviour? I did find the following info before on using multiple forwarders: https://lists.isc.org/pipermail/bind-users/2007-September/067830.html My expectation based on that is that the

"Malformed Transaction" after thawing large zone with lots of DDNS updates / BIND 9.6.0-P1

Hi, A large zone is frozen with 'rndc freeze', changes are done to the zone file, DDNS updates are enabled again with 'rndc thaw'. I can see the following series of events in the logs (filtered): 05-May-2009 13:08:10.466 notify: info: zone corp.internal.com/IN: sending notifies (serial 201241049

Current named statistics format documentation

Hi, any idea where the statistic number currently reported to the named.stats file are documented. The ARM only describes some. For BIND 9.4.1 I get the following counters ++ Name Server Statistics ++ (Legend) success referral nxrrset nxdomain recursion failure dupquerydr