Ticket #377 (new defect)
forwarding to recursor broken for delegated subzones in pdns-3.0
| Reported by: | anon | Owned by: | ahu |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | auth | Version: | 3.2 |
| Severity: | normal | Keywords: | auth recursor |
| Cc: | stef.van.dessel@… |
Description
a) i have pdns-auth listening on *.53, and forwarding recursive queries to b) localhost:5300 where the pdns-recursor is running I am authoritative for zone example.com, but have delegated blah.example.com to someone else (this is with the bind backend running) with 2.9.22 pdns will recurse for blah.example.com with 3.0 it will only give me back the glue
now I changed my setup so I don't have it happening: pdns-recursor on 127.0.0.1:53 and the auth on the external IPs.. 14:57 < Maik> If the behaviour is as described, that would seem to be a bug. Recursor forwarding is heavily deprecated, so it may have been missed in the RC phase. You can file a ticket at wiki.powerdns.com using the login info on the front page.
Please confirm if you can reproduce this behaviour with pdns-3.0. The best solution to fix this would probably be to not allow pdns anymore to forward to a recursor ;-)
14:58 < Maik> See http://cr.yp.to/djbdns/separation.html for the deprecation. 14:59 < fets> it would be nice if the deprecation was actually in the pdns docs ;-) 15:00 < Maik> Oh, it would be nice if so many things were properly documented. ;-)
