[Newbie] Bind troubleshooting

Kevin Darcy kcd at daimlerchrysler.com
Mon Jul 22 22:47:10 UTC 2002


Mathieu DESPRIEE NO SPAM wrote:

> Hi all,
>
> I'm totally new to BIND.
> I'm using a Linux 2.4 box, with bind 9.2
>
> I've configured my named daemon, and I have a curious problem :
> * All requests concerning my zone are correctly handled (maybe a bit
> slowly ? but it's just an intuition)
> * Almost all queries concerning external zones are handled correctly
> * Sometimes, I can't manage to resolve a few particular names. When I
> try a dig on such a host, I got :
>
> ***************
>  > dig www.networkcomputing.com
>
> ; <<>> DiG 9.2.0 <<>> hits.webstat.com
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached
>
> ***************
>
> But, if I add the trace option :
>  > dig +trace www.networkcomputing.com
>
> ; <<>> DiG 9.2.0 <<>> +trace www.networkcomputing.com
> ;; global options:  printcmd
> ..                       514537  IN      NS      C.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      D.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      E.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      F.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      G.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      H.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      I.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      J.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      K.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      L.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      M.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      A.ROOT-SERVERS.NET.
> ..                       514537  IN      NS      B.ROOT-SERVERS.NET.
> ;; Received 340 bytes from 62.23.151.130#53(62.23.151.130) in 19 ms
>
> com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
> ;; Received 474 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 581 ms
>
> networkcomputing.com.   172800  IN      NS      NS1.CMPNET.com.
> networkcomputing.com.   172800  IN      NS      NS2.CMPNET.com.
> ;; Received 117 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 101 ms
>
> www.networkcomputing.com. 600   IN      A       66.77.24.3
> networkcomputing.com.   86400   IN      NS      ns2.cmpnet.com.
> networkcomputing.com.   86400   IN      NS      ns1.cmpnet.com.
> ;; Received 133 bytes from 66.77.26.9#53(NS1.CMPNET.com) in 99 ms
>
> *********
>
> I don't understand anything...
>
> Can anybody explain me ?

Since this is sporadic, it's unlikely to be a BIND configuration problem.
I'd look more closely at network issues, e.g. congestion, as the source of
the problem. Your latencies seem a little high: I just did the same trace
and all of the responses came back in 58ms or less...


- Kevin




More information about the bind-users mailing list