named slow resolving to internet
Kevin Darcy
kcd at chrysler.com
Wed Oct 31 19:23:28 UTC 2007
When you have nothing cached, named needs to do the grunt work of
tracking down each referral at each level of the namespace hierarchy.
Depending on how quickly the authoritative nameservers are responding,
how messed up the delegation records and/or glue records are, network
topology, and a host of other factors, yes, the initial query can take a
second or more. Once you have all that information cached, then
typically you can either answer directly from cache, or fetch the data
straight from the authoritative nameservers for the zone.
So far you haven't shown or described anything out of the ordinary.
- Kevin
Latif wrote:
> On Oct 31, 3:05 pm, Kevin Darcy <k... at chrysler.com> wrote:
>
>> You're complaining about 154 msecs?
>>
>> It's "cache", by the way, not "catch"...
>>
>> - Kevin
>>
>>
>>
>> Latif wrote:
>>
>>> I'm running bind 9.3.2 in HP-UX 11.23 PA.
>>>
>>> It takes longer when querying the internet the first time we run dig
>>> and it takes quite sometimes before we get a response:
>>>
>>> hpadm1:/home/rootlbm > digwww.ducks.com
>>>
>>> ; <<>> DiG 9.3.2 <<>>www.ducks.com
>>>
>>> ;; global options: printcmd
>>>
>>> ;; Got answer:
>>>
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 497
>>>
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
>>>
>>> ;; QUESTION SECTION:
>>>
>>> ;www.ducks.com. IN A
>>>
>>> ;; ANSWER SECTION:
>>>
>>> www.ducks.com. 3600 IN CNAME ethel.basspro.com.
>>>
>>> ethel.basspro.com. 3600 IN A 12.14.224.133
>>>
>>> ;; AUTHORITY SECTION:
>>>
>>> basspro.com. 3600 IN NS cbru.br.ns.els-
>>> gms.att.net.
>>>
>>> basspro.com. 3600 IN NS cmtu.mt.ns.els-
>>> gms.att.net.
>>>
>>> ;; ADDITIONAL SECTION:
>>>
>>> cbru.br.ns.els-gms.att.net. 1401 IN A 199.191.128.105
>>>
>>> cmtu.mt.ns.els-gms.att.net. 1401 IN A 12.127.16.69
>>>
>>> ;; Query time: 154 msec
>>>
>>> ;; SERVER: 172.16.1.50#53(172.16.1.50)
>>>
>>> ;; WHEN: Wed Oct 31 11:48:54 2007
>>>
>>> ;; MSG SIZE rcvd: 169
>>>
>>> The next time we run it, it's already in the catch so it's faster. Are
>>> we missing a configuration for catching named?
>>>
>>> hpadm1:/home/rootlbm > digwww.ducks.com
>>>
>>> ; <<>> DiG 9.3.2 <<>>www.ducks.com
>>>
>>> ;; global options: printcmd
>>>
>>> ;; Got answer:
>>>
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1511
>>>
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
>>>
>>> ;; QUESTION SECTION:
>>>
>>> ;www.ducks.com. IN A
>>>
>>> ;; ANSWER SECTION:
>>>
>>> www.ducks.com. 3510 IN CNAME ethel.basspro.com.
>>>
>>> ethel.basspro.com. 3514 IN A 12.14.224.133
>>>
>>> ;; AUTHORITY SECTION:
>>>
>>> basspro.com. 3514 IN NS cmtu.mt.ns.els-
>>> gms.att.net.
>>>
>>> basspro.com. 3514 IN NS cbru.br.ns.els-
>>> gms.att.net.
>>>
>>> ;; ADDITIONAL SECTION:
>>>
>>> cbru.br.ns.els-gms.att.net. 375 IN A 199.191.128.105
>>>
>>> cmtu.mt.ns.els-gms.att.net. 375 IN A 12.127.16.69
>>>
>>> ;; Query time: 5 msec
>>>
>>> ;; SERVER: 172.16.1.48#53(172.16.1.48)
>>>
>>> ;; WHEN: Wed Oct 31 11:50:27 2007
>>>
>>> ;; MSG SIZE rcvd: 169- Hide quoted text -
>>>
>> - Show quoted text -
>>
>
> Well my friend, sometimes it takes longer than that..
> BTW: thanks for correcting me. It was just a typo.
>
> Any one else please with suggestions that I can use?
>
>
>
>
>
More information about the bind-users
mailing list