Strange name resolution problem
Barry Margolin
barmar at alum.mit.edu
Sat Feb 3 03:55:57 UTC 2007
In article <eq0cal$252s$1 at sf1.isc.org>,
"Bhaskar Regmi" <bhaskar.regmi at gmail.com> wrote:
> We are using bind 9.3, for the most part it's working perfectly. But
> it can't resolve some sites. "dig +trace hostname @ns" returns the
> answer but "dig hostname @ns" always times out. I simply could not
> figure out the problem.
When you use +trace, dig doesn't use recursion to resolve the name --
dig performs all the iteration itself. The server named with @ns is
only used to resolve the nameservers along the way.
>
> This lookup fails
> =======
> $ dig www.fiatifta.org @cache01
>
> ; <<>> DiG 9.2.3 <<>> www.fiatifta.org @cache01
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
>
> This lookup works
> =============
> $dig +trace www.fiatifta.org @cache01
>
> ; <<>> DiG 9.2.3 <<>> +trace www.fiatifta.org @cache01
> ;; global options: printcmd
> . 320489 IN NS M.ROOT-NET.
>
> OUTPUT TRIMMED
>
> fiatifta.org. 86400 IN NS nsr1.ina.fr.
> fiatifta.org. 86400 IN NS nsr0.ina.fr.
> ;; Received 78 bytes from 204.74.113.1#53
>
> (TLD2.ULTRADNS.NET) in 98 ms
>
> www.fiatifta.org. 86400 IN A 195.221.139.20
> www.fiatifta.org. 86400 IN A 195.221.139.21
> fiatifta.org. 86400 IN NS nsr1.ina.fr.
> fiatifta.org. 86400 IN NS nsr0.ina.fr.
> ;; Received 142 bytes from 195.221.139.126#53(nsr1.ina.fr) in 213 ms
>
> Thanks
> Bhaskar
--
Barry Margolin, barmar at alum.mit.edu
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