First time not OK but subsequent query got resolved

[Stanley Liu]

> At 09:11 PM 2/5/02, Stanley Liu wrote:
> >BIND 8.3.1 on NT.
> >
> >Could someone help me out here please?  I have a situation that every
time
> >I try to browse a URL (any valid host) the first time, it always returns
> >"page not found".  Subsequent queries are OK.  I have switched on Debug
> >level 4 in the nameserver and I have the following:
> >
In order not to confuse people who tried to help me, I now use
http://www.symantec.com as the URL (instead of URL of our own
inside.toyota.com.au):

07-Feb-2002 17:11:08.000 datagram from [198.6.49.5].53, fd 176, len 464
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 239
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
;; a568.g.akamai.net, type = A, class = IN
net.   1d22h40m47s IN NS  A.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  G.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  H.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  C.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  I.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  B.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  D.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  L.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  F.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  J.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  K.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  E.GTLD-SERVERS.net.
net.   1d22h40m47s IN NS  M.GTLD-SERVERS.net.
A.GTLD-SERVERS.net. 1d22h40m47s IN A  192.5.6.30
G.GTLD-SERVERS.net. 1d22h40m47s IN A  192.42.93.30
H.GTLD-SERVERS.net. 1d22h40m47s IN A  192.54.112.30
C.GTLD-SERVERS.net. 1d22h40m47s IN A  192.26.92.30
I.GTLD-SERVERS.net. 1d22h40m47s IN A  192.43.172.30
B.GTLD-SERVERS.net. 1d22h40m47s IN A  192.33.14.30
D.GTLD-SERVERS.net. 1d22h40m47s IN A  192.31.80.30
L.GTLD-SERVERS.net. 1d22h40m47s IN A  192.41.162.30
F.GTLD-SERVERS.net. 1d22h40m47s IN A  192.35.51.30
J.GTLD-SERVERS.net. 1d22h40m47s IN A  210.132.100.101
K.GTLD-SERVERS.net. 1d22h40m47s IN A  213.177.194.5
E.GTLD-SERVERS.net. 1d22h40m47s IN A  192.12.94.30
M.GTLD-SERVERS.net. 1d22h40m47s IN A  202.153.114.101
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 bad referral (net !< symantec.com) from
[198.6.49.5].53
07-Feb-2002 17:11:08.000 ncache: dname a568.g.akamai.net, type 1, class 1
07-Feb-2002 17:11:08.000 db_update failed (-10), cache_n_resp()
07-Feb-2002 17:11:08.000 Cname second pass
07-Feb-2002 17:11:08.000 resp: nlookup(www.symantec.com) qtype=1
07-Feb-2002 17:11:08.000 resp: found 'www.symantec.com' as
'www.symantec.com' (cname=0)
07-Feb-2002 17:11:08.000 finddata(): buflen=4062
07-Feb-2002 17:11:08.000 ns_resp: query(www.symantec.com) No possible A RRs
07-Feb-2002 17:11:08.000 send_msg -> [150.45.153.14].1167 (UDP 160) id=1
evSetTimer(ctx 0x8a0020, func 0x413a90, uap 0, due 1013062275.000000000,
inter 0.000000000)
pselect(177, 0xf5f5f5f5, 0xf5f5f5f5, 0xf5f5f5f5, 7.000000000)
select() returns 1 (err: none)

What I also found was that I can call up the page a few times immediate
before without problem (each time shutting down the browser and re-open
again) and then suddenly BIND logs the above error and the browser displayed
"The page cannot be displayed".  (So may be the subject line of my post
should read as "inconsistent response from BIND as resolver for domain with
referral").

Danny Mayer previously commented on the message line of "ncache: dname
a568.g.akamai.net, type 1, class 1" and that the problem could be caused by
the existence of "dname". However, I have tried another totally different
URL (inside.toyota.com.au) and has logged the same error message.  The
chance of both nameservers sending out "dname" response should be pretty
slim.  I for a start know that inside.toyota.com.au do not have dname RR.
So where does the "dname" comes from?  May be someone could help.  Thanks.

I run BIND 8.3.1 on NT 4.0.

Stanley Liu
stanley.liu at toyota.com.au