dns: prevent creation of cross-tenant conflicting DNS zones in the same server - #13946
Open
winterhazel wants to merge 2 commits into
Open
dns: prevent creation of cross-tenant conflicting DNS zones in the same server#13946winterhazel wants to merge 2 commits into
winterhazel wants to merge 2 commits into
Conversation
Member
Author
|
@blueorangutan package |
weizhouapache
approved these changes
Aug 21, 2026
Member
|
lgtm |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #13946 +/- ##
=========================================
Coverage 19.72% 19.73%
- Complexity 19944 19951 +7
=========================================
Files 6371 6371
Lines 575738 575765 +27
Branches 70471 70478 +7
=========================================
+ Hits 113587 113614 +27
+ Misses 449805 449798 -7
- Partials 12346 12353 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
allocateDnsZoneallows users to register DNS zones that conflict with DNS zones from the same server belonging to other users, which consequently allows them to shadow DNS records belonging to other users.Example: Victim tenant runs
tenant1.cloud.examplewith www → 203.0.113.10 on a shared public server (suffixcloud.example). A co-tenant callscreateDnsZone name=www.tenant1.cloud.example dnsserverid=<shared>— accepted as-is — then adds an apex A record to their own IP; every resolver using that PowerDNS now resolves the victim's hostname to the attacker.This patch rejects zones that overlap another tenant's zone as either a DNS parent or child, and also requires a non-blank
publicDomainSuffixfor public servers. It was mostly generated using AI tools, but reviewed and tested by a human.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I reproduced the example scenario before the patch, and verified that it is not reproducible anymore after the changes.