Reciving Timeout from DNS Server for a zone file Not present in named.conf.
bmcdonaldjr at gmail.com
Thu Jul 9 00:20:30 UTC 2015
1) status REFUSED - server with recursion turned off. with or without
+norecurse on the dig command.
2) status NXDOMAIN - server with recursion turned on with or without
+norecurse on the dig command (and access to the internet in my case)
3) status may be NOERROR depending on if a forwarder can resolve that zone.
I'm on ubuntu with bind 9.9.5 (current level of bind9 from ubuntu 14.04.02
4) Forgive my being a bit naive but isn't it e164.arpa. instead of e164.ld.
? l don't recall ld being a valid TLD. (That might affect your response)
5) YMMV with other Linux distros or other unixes because of differing bind
versions (but probably not)
>Date: Wed, 08 Jul 2015 12:38:20 -0400
>From: Barry Margolin <barmar at alum.mit.edu>
>To: comp-protocols-dns-bind at isc.org
>Subject: Re: Receiving Timeout from DNS Server for a zone file Not
> present in named.conf
>Message-ID: <barmar-25F285.12382008072015 at 88-209-239-213.giganet.hu>
>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>
>> 22.214.171.124.126.96.36.199.6.9.1.e164.ld. NAPTR
>> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>>
>> 188.8.131.52.184.108.40.206.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
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users