Another Question about SERVFAIL

Josh Kuo josh.kuo at gmail.com
Tue May 25 22:51:35 UTC 2010


I tried these myself, and I am still scratching my head on the results.
First, I tried to look for just ftp.cisco.com's A record, and I got back the
answer 198.133.219.241.

$ dig @4.2.2.2 ftp.cisco.com. a

; <<>> DiG 9.4.3-P3 <<>> @4.2.2.2 ftp.cisco.com. a
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60411
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;ftp.cisco.com.                 IN      A

;; ANSWER SECTION:
ftp.cisco.com.          60      IN      A       198.133.219.241

;; AUTHORITY SECTION:
ftp.cisco.com.          85449   IN      NS      rtp5-ddir-ns.cisco.com.
ftp.cisco.com.          85449   IN      NS      sjce-ddir-ns.cisco.com.

;; ADDITIONAL SECTION:
sjce-ddir-ns.cisco.com. 85501   IN      A       128.107.240.86

;; Query time: 184 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Tue May 25 15:48:43 2010
;; MSG SIZE  rcvd: 117

... BUT, if I tried to look for any record, I get a very different answer:

$ dig @4.2.2.2 ftp.cisco.com. any

; <<>> DiG 9.4.3-P3 <<>> @4.2.2.2 ftp.cisco.com. any
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53036
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Messages has 2 extra bytes at end

;; QUESTION SECTION:
;ftp.cisco.com.                 IN      ANY

;; ANSWER SECTION:
ftp.cisco.com.          50      IN      A       169.254.1.1

;; Query time: 640 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Tue May 25 15:45:58 2010
;; MSG SIZE  rcvd: 49


Any thoughts on why? I do notice the warning message that the message has 2
extra bytes at the end, perhaps it's a malformed response for the 'any' RR
query?


>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20100525/afd88c4d/attachment.html>


More information about the bind-users mailing list