| |||||||||||||||||||||||||||||||
|
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 > dig www.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 > dig www.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
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com