Receiving Timeout from DNS Server for a zone file Not present in named.conf
barmar at alum.mit.edu
Wed Jul 8 16:38:20 UTC 2015
In article <mailman.2239.1436350643.26362.bind-users at lists.isc.org>,
Harshith Mulky <harshith.mulky at outlook.com> wrote:
> I have a query here,
> I have named.conf configured But I do not have zone file configured for a
> domain name as "e164.ld"
> I am sending out a query asdig @<DNS Server IP>
> 184.108.40.206.220.127.116.11.6.9.1.e164.ld. NAPTR
> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>>
> 18.104.22.168.22.214.171.124.6.9.1.e164.ld. NAPTR;; global options: +cmd;; connection
> timed out; no servers could be reached
> I am receiving a Connection TimeOut message
> Should not i be receiving a NXDOMAIN response from DNS Server?
> What are the scenarios, I will be receiving a Timeout, or a NXDOMAIN, or a
> REFUSED from DNS Server
> I have Installed BIND on RHEL system! Would the reposnes be different in
> different servers like Linux, Solaris, CENTOS?
Since you didn't use the +norecurse option, the server will try to make
a recursive query for you (assuming you're in its allow-recursion access
list). If dig times out before that completes, you'll get a timeout
More information about the bind-users