Bind 9.4.2 not resolving one domain

caio elcaio at gmail.com
Thu Sep 4 17:58:22 UTC 2008


Chris Buxton escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> There are other known examples. One that springs to mind is:
> 
> www.microsoft.com.    3063    IN    CNAME    toggle.www.ms.akadns.net.
> toggle.www.ms.akadns.net. 58    IN    CNAME    g.www.ms.akadns.net.
> g.www.ms.akadns.net.    58    IN    CNAME    lb1.www.ms.akadns.net.
> lb1.www.ms.akadns.net.    58    IN    A    65.55.11.222
> lb1.www.ms.akadns.net.    58    IN    A    207.46.19.190
> lb1.www.ms.akadns.net.    58    IN    A    207.46.19.254
> lb1.www.ms.akadns.net.    58    IN    A    207.46.193.254
> lb1.www.ms.akadns.net.    58    IN    A    65.55.21.250
> lb1.www.ms.akadns.net.    58    IN    A    207.46.192.254
> 
> However, this is still only two main lookup chains, instead of three 
> like www.yahoo.com.ar. I count around 8 lookups (minimum) to get this 
> answer when starting with an empty cache.
> 
> I would be more inclined to suspect network connectivity problems with 
> the lookup you're having problems with. With that many lookups, each one 
> needs to complete in a reasonable amount of time - 50 ms on average, or 
> thereabouts, to complete the whole thing in 5 seconds. How is your 
> connection to the various servers involved? These are the servers 
> authoritative for:
> 
> .
> ar.
> com.ar.
> yahoo.com.ar.
> com.
> yahoo.com.
> g1.b.yahoo.com.
> a1.b.yahoo.com.
> 
> Note that yahoo.com.ar and yahoo.com are served by the same servers. 
> Also, the last item is hosted on a subset of the same servers as the 
> next-to-last item.
> 
> Chris Buxton
> Professional Services
> Men & Mice
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> 
> iEYEARECAAYFAki/8pIACgkQ0p/8Jp6Boi2NBgCfXD7sgbydnBbAb/vk6oaa0S+N
> 6DcAn25rbZ1dVtWVhe4jkhS3EHIvcQEt
> =sn6l
> -----END PGP SIGNATURE-----

do not know if a connectivity problem, because i have 2 name servers, at 
the same network level hierarchy (but differents subnet).., and maybe 
there is one working ok while the other with failure..

here the case of the secondary ns...(at this moment):

# dig @dns2.mydomain.com www.yahoo.com.ar +trace
; <<>> DiG 9.4.2 <<>> @dns2.mydomain.com www.yahoo.com.ar +trace
; (1 server found)
;; global options:  printcmd
.                       446409  IN      NS      A.ROOT-SERVERS.NET.
.                       446409  IN      NS      M.ROOT-SERVERS.NET.
.                       446409  IN      NS      L.ROOT-SERVERS.NET.
.                       446409  IN      NS      J.ROOT-SERVERS.NET.
.                       446409  IN      NS      C.ROOT-SERVERS.NET.
.                       446409  IN      NS      H.ROOT-SERVERS.NET.
.                       446409  IN      NS      B.ROOT-SERVERS.NET.
.                       446409  IN      NS      E.ROOT-SERVERS.NET.
.                       446409  IN      NS      G.ROOT-SERVERS.NET.
.                       446409  IN      NS      I.ROOT-SERVERS.NET.
.                       446409  IN      NS      D.ROOT-SERVERS.NET.
.                       446409  IN      NS      K.ROOT-SERVERS.NET.
.                       446409  IN      NS      F.ROOT-SERVERS.NET.
;; Received 352 bytes from <dns2_public_ip_addr>#53(ip_addr) in 0 ms

ar.                     172800  IN      NS      NS.UU.NET.
ar.                     172800  IN      NS      NS1.RETINA.ar.
ar.                     172800  IN      NS      ATHEA.ar.
ar.                     172800  IN      NS      CTINA.ar.
ar.                     172800  IN      NS      NS-AR.RIPE.NET.
ar.                     172800  IN      NS      MERAPI.SWITCH.CH.
ar.                     172800  IN      NS      UUCP-GW-1.PA.DEC.COM.
ar.                     172800  IN      NS      UUCP-GW-2.PA.DEC.COM.
;; Received 391 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 484 ms

yahoo.com.ar.           14400   IN      NS      ns1.yahoo.com.
yahoo.com.ar.           14400   IN      NS      ns3.yahoo.com.
yahoo.com.ar.           14400   IN      NS      ns4.yahoo.com.
yahoo.com.ar.           14400   IN      NS      ns5.yahoo.com.
;; Received 115 bytes from 137.39.1.3#53(NS.UU.NET) in 173 ms

www.yahoo.com.ar.       1800    IN      CNAME   hp2.latam.g1.b.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf1.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf2.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf3.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf4.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf5.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf6.yahoo.com.
g1.b.yahoo.com.         172800  IN      NS      yf7.yahoo.com.
;; Received 310 bytes from 66.218.71.63#53(ns1.yahoo.com) in 233 ms

And without "+trace" argument:

# dig @dns2.mydomain.com www.yahoo.com.ar

; <<>> DiG 9.4.2 <<>> @dns2.mydomain.com www.yahoo.com.ar
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached

Why with 'trace' the query seem to finish, and without 'trace' it fails?

--
caio


More information about the bind-users mailing list