-
Notifications
You must be signed in to change notification settings - Fork 908
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
auth: allow turning off across-zone resolving #14604
base: master
Are you sure you want to change the base?
Conversation
Ideas on how to add regression-tests welcome. |
Pull Request Test Coverage Report for Build 11065599865Details
💛 - Coveralls |
033c2a4
to
67cb459
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about SVCB?
Is there currently some code in PDNS to follow SVCB? SVCB ist quite different as the client application needs to perform the resolving. But IMO PDNS should not provide hints out of bailiwik, regardless if CNAME, DNAME, SVCB/HTTPS, NS .... |
SVCB was taken care of by #10521 |
308ca1e
to
c724660
Compare
c724660
to
26d9e11
Compare
Default is unchanged. Turning off the new setting causes CNAME targets to not be followed across (local) zones. Also, queries that could be answered by following a local delegations are similarly not resolved.
26d9e11
to
b031eeb
Compare
Also added regression test. |
Short description
Addresses #10017. Introduces new setting
resolve-across-zones
. Default is the unchanged behaviour.Turning off the new setting causes CNAME targets to not be followed across (local) zones. Also, queries that could be answered by following a local delegation are similarly not resolved.
Checklist
I have: