Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

additional-processing=on not working on recursor 3.6.0-rc1 #1448

Closed
mortenstevens opened this issue Jun 2, 2014 · 2 comments
Closed

additional-processing=on not working on recursor 3.6.0-rc1 #1448

mortenstevens opened this issue Jun 2, 2014 · 2 comments

Comments

@mortenstevens
Copy link
Contributor

additional-processing=on doesn't work since recursor 3.5.x

my config:

setuid=pdns-recursor
setgid=pdns-recursor
local-address=127.0.0.1, 10.0.0.70
local-port=53
additional-processing=on
allow-from-file=/etc/pdns-recursor/access.conf
dig ns powerdns.com

; <<>> DiG 9.9.4-RedHat-9.9.4-14.el7 <<>> ns powerdns.com ;; global options: +cmd ;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35097 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;powerdns.com.                  IN      NS

;; ANSWER SECTION:
powerdns.com.           3597    IN      NS      powerdnssec1.ds9a.nl.
powerdns.com.           3597    IN      NS      powerdnssec2.ds9a.nl.

;; Query time: 1 msec
;; SERVER: 10.0.0.70#53(10.0.0.70)
;; WHEN: Sat May 31 16:04:08 CEST 2014
;; MSG SIZE  rcvd: 91

Result: The additional section is still missing.

Expected result:

;; ADDITIONAL SECTION:
powerdnssec2.ds9a.nl.   380     IN      A       178.63.8.86
powerdnssec2.ds9a.nl.   380     IN      AAAA    2a01:4f8:110:4389::2
powerdnssec1.ds9a.nl.   380     IN      A       82.94.213.34
powerdnssec1.ds9a.nl.   380     IN      AAAA    2001:888:2000:1d::2
@Habbie
Copy link
Member

Habbie commented Jun 3, 2014

Can confirm, this option (and its v6 counterpart) don't actually do anything right now (since 21f0f88). Will discuss.

@Habbie
Copy link
Member

Habbie commented Jun 3, 2014

As this has been "broken" since before 3.5, and nobody has reported actual problems resulting from it, we have decided to delete the dead code. A feature request ticket (with motivation) would be considered after 3.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants