To deal with inproper nodata notification

Liu Mingxing lmxhappy at gmail.com
Sat May 11 06:14:12 UTC 2013


I found that bind9.9.2 recursor returns servfail to  soa requests when receiving inproper nodata notification that there is just a root SOA RR in the authority section in response from authoritative namservers.
Just like this as following.   Why does it forward the inproper response to clients?


 [root at localhost secman]# dig soft.vipbiz.cn ns @localhost

; <<>> DiG 9.9.2-P2 <<>> soft.vipbiz.cn ns @localhost
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21576
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;soft.vipbiz.cn.                        IN      NS

;; Query time: 91 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri May 10 23:08:56 2013
;; MSG SIZE  rcvd: 43





Liu Mingxing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130511/d4e9d27c/attachment.html>


More information about the bind-users mailing list