Weird dig behavior when querying ANY

Nicholas F Miller nicholas.miller at Colorado.EDU
Tue Sep 10 14:15:57 UTC 2013


I am at a loss. When doing digs using our name servers for 'ANY' records of a domain we are getting TTLs of five seconds. The TTLs will be correct if we query for the records individually just not when using 'ANY'. Ideas?

> dig google.com any

; <<>> DiG 9.8.3-P1 <<>> google.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30827
;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com.                    IN      ANY

;; ANSWER SECTION:
google.com.             5       IN      AAAA    2607:f8b0:400f:801::1000
google.com.             5       IN      SOA     ns1.google.com. dns-admin.google.com. 2013082900 7200 1800 1209600 300
google.com.             5       IN      A       74.125.225.193
google.com.             5       IN      A       74.125.225.196
google.com.             5       IN      A       74.125.225.200
google.com.             5       IN      A       74.125.225.197
google.com.             5       IN      A       74.125.225.192
google.com.             5       IN      A       74.125.225.201
google.com.             5       IN      A       74.125.225.194
google.com.             5       IN      A       74.125.225.195
google.com.             5       IN      A       74.125.225.198
google.com.             5       IN      A       74.125.225.206
google.com.             5       IN      A       74.125.225.199
google.com.             5       IN      NS      ns2.google.com.
google.com.             5       IN      NS      ns4.google.com.
google.com.             5       IN      NS      ns3.google.com.
google.com.             5       IN      NS      ns1.google.com.

;; AUTHORITY SECTION:
google.com.             18135   IN      NS      ns3.google.com.
google.com.             18135   IN      NS      ns4.google.com.
google.com.             18135   IN      NS      ns1.google.com.
google.com.             18135   IN      NS      ns2.google.com.

;; ADDITIONAL SECTION:
ns1.google.com.         210081  IN      A       216.239.32.10
ns2.google.com.         215921  IN      A       216.239.34.10
ns3.google.com.         215921  IN      A       216.239.36.10
ns4.google.com.         210081  IN      A       216.239.38.10

;; Query time: 0 msec
;; SERVER: 128.138.129.76#53(128.138.129.76)
;; WHEN: Tue Sep 10 07:55:14 2013
;; MSG SIZE  rcvd: 470

--

> dig google.com ns

; <<>> DiG 9.8.3-P1 <<>> google.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56530
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com.                    IN      NS

;; ANSWER SECTION:
google.com.             16952   IN      NS      ns1.google.com.
google.com.             16952   IN      NS      ns2.google.com.
google.com.             16952   IN      NS      ns4.google.com.
google.com.             16952   IN      NS      ns3.google.com.

;; ADDITIONAL SECTION:
ns1.google.com.         208898  IN      A       216.239.32.10
ns2.google.com.         214738  IN      A       216.239.34.10
ns3.google.com.         214738  IN      A       216.239.36.10
ns4.google.com.         208898  IN      A       216.239.38.10

;; Query time: 0 msec
;; SERVER: 128.138.129.76#53(128.138.129.76)
;; WHEN: Tue Sep 10 08:14:57 2013
;; MSG SIZE  rcvd: 164
_________________________________________________________
Nicholas Miller, OIT, University of Colorado at Boulder






More information about the bind-users mailing list