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

auth: allow turning off across-zone resolving #14604

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

zeha
Copy link
Collaborator

@zeha zeha commented Aug 28, 2024

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:

  • read the CONTRIBUTING.md document
  • compiled this code
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)

@zeha
Copy link
Collaborator Author

zeha commented Aug 28, 2024

Ideas on how to add regression-tests welcome.

@coveralls
Copy link

coveralls commented Aug 28, 2024

Pull Request Test Coverage Report for Build 11065599865

Details

  • 6 of 10 (60.0%) changed or added relevant lines in 2 files are covered.
  • 47 unchanged lines in 14 files lost coverage.
  • Overall coverage increased (+0.03%) to 64.699%

Changes Missing Coverage Covered Lines Changed/Added Lines %
pdns/packethandler.cc 5 9 55.56%
Files with Coverage Reduction New Missed Lines %
pdns/pollmplexer.cc 1 83.66%
pdns/recursordist/aggressive_nsec.cc 2 66.32%
pdns/distributor.hh 2 51.86%
pdns/misc.cc 2 63.26%
pdns/recursordist/test-syncres_cc2.cc 3 88.91%
pdns/misc.hh 3 87.62%
pdns/recursordist/recpacketcache.hh 3 89.55%
pdns/remote_logger.cc 3 53.81%
modules/gpgsqlbackend/spgsql.cc 3 67.46%
pdns/recursordist/rec-tcp.cc 4 65.34%
Totals Coverage Status
Change from base Build 11055633944: 0.03%
Covered Lines: 124841
Relevant Lines: 162232

💛 - Coveralls

@zeha zeha force-pushed the zeha-10017-cname-follow-config branch from 033c2a4 to 67cb459 Compare August 28, 2024 13:49
@Habbie Habbie self-requested a review September 3, 2024 12:12
Copy link
Member

@Habbie Habbie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about SVCB?

docs/settings.rst Outdated Show resolved Hide resolved
@Habbie Habbie added this to the auth-5 milestone Sep 5, 2024
@klaus-nicat
Copy link
Contributor

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 ....

@zeha
Copy link
Collaborator Author

zeha commented Sep 23, 2024

what about SVCB?

SVCB was taken care of by #10521

@Habbie Habbie self-requested a review September 23, 2024 11:45
@zeha zeha force-pushed the zeha-10017-cname-follow-config branch 2 times, most recently from 308ca1e to c724660 Compare September 26, 2024 08:50
@zeha zeha changed the title auth: allow turning off across-domain resolving auth: allow turning off across-zone resolving Sep 26, 2024
@zeha zeha force-pushed the zeha-10017-cname-follow-config branch from c724660 to 26d9e11 Compare September 26, 2024 09:53
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.
@zeha zeha force-pushed the zeha-10017-cname-follow-config branch from 26d9e11 to b031eeb Compare September 27, 2024 06:21
@zeha
Copy link
Collaborator Author

zeha commented Sep 27, 2024

Also added regression test.

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

Successfully merging this pull request may close these issues.

5 participants