BIND 9 AAAA record problems

[wbwither at bobball.uchicago.edu]

Kevin Darcy <kcd at daimlerchrysler.com> wrote:

> Caching should make the response quicker, not slower, but you might
> want  to talk to your ISP to see if they are doing anything funky.

Err, right.  I meant that maybe they were caching the old answer, or
non-answer as the case may be?  I'm still getting some slow responses when
I dig @ my ISP's DNS server, and some slow page-load times when I try to
view the webpage from my Linux machine....
bash-2.05b$ dig @216.167.161.35 efori.com IN AAAA

; <<>> DiG 8.3 <<>> @216.167.161.35 efori.com IN AAAA
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend: Operation timed out

but if I dig at a different nameserver:

wbwither at bobball:~$ dig @128.135.12.73 efori.com IN AAAA

; <<>> DiG 9.2.1 <<>> @128.135.12.73 efori.com IN AAAA
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54325
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;efori.com.                     IN      AAAA

;; AUTHORITY SECTION:
efori.com.              8962    IN      SOA     dns1.efori.com.
hostmaster.efori.com. 2004061701 86400 7200 3600000 345600
;; Query time: 4 msec
;; SERVER: 128.135.12.73#53(128.135.12.73)
;; WHEN: Wed Jun 23 14:33:32 2004
;; MSG SIZE  rcvd: 79

Thanks for your help,

-Brock