BIND 9 with views recursion issues

Barry Margolin barmar at
Wed Nov 15 03:10:20 UTC 2006

In article <ejctr4$27hj$1 at>,
 "FredrichManey" <fredrichmaney at> wrote:

> More detail......
> When diagnosing the issue I get truly odd and inconsistent results. By
> specifying different options to 'dig' I can sometimes resolve, and
> sometimes not.
> For example, one of the sites that is failing is
> Here's the output from 'dig' with various options:
> root at dns02# dig @
> ; <<>> DiG 9.3.2 <<>> @
> ; (1 server found)
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached
> root at dns02# dig @ +trace
> ; <<>> DiG 9.3.2 <<>> @ +trace
> ; (1 server found)

Using +trace is almost never a good way to test a caching server.  This 
option causes dig to do its own iteration starting from the root 
servers, rather than asking the caching server to recurse.  I think it 
only uses the caching server to resolve the hostnames in NS records, it 
doesn't use it to resolve the name you're actually trying to look up.

Barry Margolin, barmar at
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

More information about the bind-users mailing list