Recursive Replies

prock111 at yahoo.com prock111 at yahoo.com
Thu Feb 11 19:18:59 UTC 2010


The following two DIG replies were obtained in a closed lab for the same query.  Note the Header and Answer sections are similar (the response ID was stripped out).  But the Authority and Additional sections of the response differ.

My questions:  These responses are not wrong.  They are differnet, but not wrong.  Would you agree?

Second question is: is there a way to make a recursive NS provide the same response to a query?  (Minus the ID data in the header section of course.)  In the example below, is there a setting in named.conf (or anything else) that can provide the same response for a query?  (thanks)

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 31, AUTHORITY: 7, ADDITIONAL: 14
;; QUESTION SECTION:
;a.test.com. IN AAAA
;; ANSWER SECTION:
a.test.com. in aaaa   a:b:c:d:e:f:f:55
a.test.com. in aaaa   a:b:c:d:e:f:f:56
a.test.com. in aaaa   a:b:c:d:e:f:f:57
a.test.com. in aaaa   a:b:c:d:e:f:f:58
a.test.com. in aaaa   a:b:c:d:e:f:f:59
a.test.com. in aaaa   a:b:c:d:e:f:f:60
a.test.com. in aaaa   a:b:c:d:e:f:f:61
a.test.com. in aaaa   a:b:c:d:e:f:f:62
a.test.com. in aaaa   a:b:c:d:e:f:f:63
a.test.com. in aaaa   a:b:c:d:e:f:f:64
a.test.com. in aaaa   a:b:c:d:e:f:f:65
a.test.com. in aaaa   a:b:c:d:e:f:f:66
a.test.com. in aaaa   a:b:c:d:e:f:f:67
a.test.com. in aaaa   a:b:c:d:e:f:f:68
a.test.com. in aaaa   a:b:c:d:e:f:f:69
a.test.com. in aaaa   a:b:c:d:e:f:f:70
a.test.com. in aaaa   a:b:c:d:e:f:f:71
a.test.com. in aaaa   a:b:c:d:e:f:f:72
a.test.com. in aaaa   a:b:c:d:e:f:f:73
a.test.com. in aaaa   a:b:c:d:e:f:f:74
a.test.com. in aaaa   a:b:c:d:e:f:f:75
a.test.com. in aaaa   a:b:c:d:e:f:f:76
a.test.com. in aaaa   a:b:c:d:e:f:f:77
a.test.com. in aaaa   a:b:c:d:e:f:f:78
a.test.com. in aaaa   a:b:c:d:e:f:f:79
a.test.com. in aaaa   a:b:c:d:e:f:f:80
a.test.com. in aaaa   a:b:c:d:e:f:f:81
a.test.com. in aaaa   a:b:c:d:e:f:f:82
a.test.com. in aaaa   a:b:c:d:e:f:f:83
a.test.com. in aaaa   a:b:c:d:e:f:f:84
a.test.com. in aaaa   a:b:c:d:e:f:f:85
;; AUTHORITY SECTION:
com.                    in      ns      a.gtld-servers.com.
com.                    in      ns      c.gtld-servers.com.
com.                    in      ns      d.gtld-servers.com.
com.                    in      ns      e.gtld-servers.com.
com.                    in      ns      f.gtld-servers.com.
com.                    in      ns      g.gtld-servers.com.
com.                    in      ns      l.gtld-servers.com.
;; ADDITIONAL SECTION:
a.gtld-servers.com.     in      a       192.168.5.10
a.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
c.gtld-servers.com.     in      a       192.168.5.10
c.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
d.gtld-servers.com.     in      a       192.168.5.10
d.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
e.gtld-servers.com.     in      a       192.168.5.10
e.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
f.gtld-servers.com.     in      a       192.168.5.10
f.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
g.gtld-servers.com.     in      a       192.168.5.10
g.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d
l.gtld-servers.com.     in      a       192.168.5.10
l.gtld-servers.com.     in      aaaa    2001:4f8:0:2::d



;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 31, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;a.test.com. IN AAAA
;; ANSWER SECTION:
a.test.com. in aaaa   a:b:c:d:e:f:f:55
a.test.com. in aaaa   a:b:c:d:e:f:f:56
a.test.com. in aaaa   a:b:c:d:e:f:f:57
a.test.com. in aaaa   a:b:c:d:e:f:f:58
a.test.com. in aaaa   a:b:c:d:e:f:f:59
a.test.com. in aaaa   a:b:c:d:e:f:f:60
a.test.com. in aaaa   a:b:c:d:e:f:f:61
a.test.com. in aaaa   a:b:c:d:e:f:f:62
a.test.com. in aaaa   a:b:c:d:e:f:f:63
a.test.com. in aaaa   a:b:c:d:e:f:f:64
a.test.com. in aaaa   a:b:c:d:e:f:f:65
a.test.com. in aaaa   a:b:c:d:e:f:f:66
a.test.com. in aaaa   a:b:c:d:e:f:f:67
a.test.com. in aaaa   a:b:c:d:e:f:f:68
a.test.com. in aaaa   a:b:c:d:e:f:f:69
a.test.com. in aaaa   a:b:c:d:e:f:f:70
a.test.com. in aaaa   a:b:c:d:e:f:f:71
a.test.com. in aaaa   a:b:c:d:e:f:f:72
a.test.com. in aaaa   a:b:c:d:e:f:f:73
a.test.com. in aaaa   a:b:c:d:e:f:f:74
a.test.com. in aaaa   a:b:c:d:e:f:f:75
a.test.com. in aaaa   a:b:c:d:e:f:f:76
a.test.com. in aaaa   a:b:c:d:e:f:f:77
a.test.com. in aaaa   a:b:c:d:e:f:f:78
a.test.com. in aaaa   a:b:c:d:e:f:f:79
a.test.com. in aaaa   a:b:c:d:e:f:f:80
a.test.com. in aaaa   a:b:c:d:e:f:f:81
a.test.com. in aaaa   a:b:c:d:e:f:f:82
a.test.com. in aaaa   a:b:c:d:e:f:f:83
a.test.com. in aaaa   a:b:c:d:e:f:f:84
a.test.com. in aaaa   a:b:c:d:e:f:f:85
;; AUTHORITY SECTION:
test.com.       in      ns      ns1.test.com.




      



More information about the bind-users mailing list