Why does dig report one more record in the additional section of a query response than I am seeing?
- Updated on 05 Feb 2014
- 1 minute to read
This is not a bug, and it is not new behavior, although those newly upgrading to BIND 9.9 from earlier versions may have encountered it for the first time there.
From BIND 9.9.0 and newer, dig has changed its defaults:
- dig now defaults to using options "+adflag" and "+edns=0" which better reflect the behaviour of BIND and many other modern nameservers when recursing. Additionally "+dnssec" will be automatically enabled when running "dig +trace". [RT #23497]
Responses from servers that support EDNS0 will include the OPT RR, which has no text rdata format so it isn't printed, but you can see it described in comments above the question section as "OPT PSEUDOSECTION".
;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 4000
The dig utility has always counted the OPT pseudo-record in the count of additional records, but this wouldn't have been noticed by users of older versions of dig unless they manually specified the additional options (usually to observe DNSSEC material in the query responses).
© 2001-2018 Internet Systems Consortium For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership. ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.