servfail when refresh aws.amazon.com

Eric Yiu eric.yiu at gmail.com
Wed Jun 22 11:26:06 UTC 2011


Hi,

I am using bind9.7.3-P1 with solaris10x86.  I notice that
sometimes our bind server will reply servfail when querying
a zone aws.amazon.com which is expiring, while this
aws.amazon.com only 60sec cache lifetime, eg.

> /usr/local/bin/dig a aws.amazon.com

; <<>> DiG 9.7.3-P1 <<>> a aws.amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26307
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 1

;; QUESTION SECTION:
;aws.amazon.com.                        IN      A

;; ANSWER SECTION:
aws.amazon.com.         1       IN      A       72.21.210.163

;; AUTHORITY SECTION:
aws.amazon.com.         6517    IN      NS      ns-932.amazon.com.
aws.amazon.com.         6517    IN      NS      ns-931.amazon.com.
aws.amazon.com.         6517    IN      NS      ns-912.amazon.com.
aws.amazon.com.         6517    IN      NS      ns-923.amazon.com.
aws.amazon.com.         6517    IN      NS      ns-911.amazon.com.
aws.amazon.com.         6517    IN      NS      ns-921.amazon.com.

;; ADDITIONAL SECTION:
ns-911.amazon.com.      3108    IN      A       207.171.178.13

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 22 18:59:30 2011
;; MSG SIZE  rcvd: 190

> /usr/local/bin/dig a aws.amazon.com

; <<>> DiG 9.7.3-P1 <<>> a aws.amazon.com
;; global options: +cmd
;; Got answer:
*;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20884
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0*

;; QUESTION SECTION:
;aws.amazon.com.                        IN      A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 22 18:59:31 2011
;; MSG SIZE  rcvd: 32

> /usr/local/bin/dig a aws.amazon.com
^[[A
; <<>> DiG 9.7.3-P1 <<>> a aws.amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47970
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 1

;; QUESTION SECTION:
;aws.amazon.com.                        IN      A

;; ANSWER SECTION:
aws.amazon.com.         60      IN      A       72.21.210.163

;; AUTHORITY SECTION:
aws.amazon.com.         6516    IN      NS      ns-932.amazon.com.
aws.amazon.com.         6516    IN      NS      ns-911.amazon.com.
aws.amazon.com.         6516    IN      NS      ns-912.amazon.com.
aws.amazon.com.         6516    IN      NS      ns-931.amazon.com.
aws.amazon.com.         6516    IN      NS      ns-921.amazon.com.
aws.amazon.com.         6516    IN      NS      ns-923.amazon.com.

;; ADDITIONAL SECTION:
ns-911.amazon.com.      3107    IN      A       207.171.178.13

;; Query time: 229 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 22 18:59:31 2011
;; MSG SIZE  rcvd: 190



Is it normal?  What would be the problem?

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


More information about the bind-users mailing list