Here are the two results:
;; res_mkquery(0, www.go-fly.com, 1, 1)
timeout (5 secs)
timeout (10 secs)
timeout (20 secs)
opcode = QUERY, id = 40100, rcode = SERVFAIL
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0
www.go-fly.com, type = A, class = IN
*** qthvs5.qthv.quintiles.com can't find www.go-fly.com.: Server failed
And now for DIG:
; <<>> DiG 2.0 <<>> www.go-fly.com.
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 7
;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 2, Addit: 2
;; www.go-fly.com, type = A, class = IN
www.go-fly.com. 86061 A 126.96.36.199
;; AUTHORITY RECORDS:
GO-FLY.com. 172461 NS NS0.BT.NET.
GO-FLY.com. 172461 NS NS1.BT.NET.
;; ADDITIONAL RECORDS:
NS0.BT.NET. 140779 A 188.8.131.52
NS1.BT.NET. 140779 A 184.108.40.206
;; Sent 2 pkts, answer found in time: 188 msec
;; FROM: qthvs5 to SERVER: default -- 10.52.51.51
;; WHEN: Wed Feb 2 08:14:16 2000
;; MSG SIZE sent: 32 rcvd: 132
I understand SERVFAIL, here's a cut and paste from Barry Margolin:
SERVFAIL means that the server isn't able to answer properly for some
reason. It can come from a caching server if it didn't get an answer from
any of the servers that the domain is delegated to. It can also come from
a server if it notices that the domain is delegated to itself, but it
doesn't have the zone loaded and the answer isn't in its cache.
What I'm not sure about is the resolver issue. Obviously, the server NS0.BT.NET.
is resovling correctly, but only to DIG. Therefore, there must be difference
between 'nslookup' and 'dig'. ( Oh really!). I have read that 'dig' uses a
different resolver resource. Could this be the answer?
Is it possible to upgrade resolvers separately, or only by upgrading the BIND
can you upgrade the resolver?
cc: (bcc: Philip Wolfe/QRED/Quintiles)
Subject: Re: dig works, but nslookup fails?
> I currently have BIND 4.9.4, and will be upgrading, almost immediately,
> I have a question.
> My current server fails with nslookup on some sites, so I downloaded dig.
> time you say. I agree!
> Question: My nslookup fails, but DIG resolves the site:
> Example sites I'm having trouble with are:
> Is the resolver the problem causing nslookup and the named server to fail? I
> have read that DIG uses other resources for its resovler. Is this true?
> If that's the case, can I simple upgrade my resolver somehow?
I can resolve both of those using nslookup (the first time I queried
www.pharmweb.net, the query timed out, but the answer must have made it late
to the local nameserver, since it was in cache when I queried it a few seconds
What does nslookup's debug mode tell you? Are the queries just timing out? Maybe
the only difference is in the timeout settings for DiG versus nslookup...