DNS Framework: tenants cannot own DNS servers or vanity zones (no account/domainid on addDnsServer/createDnsZone)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- backend-api-design
Research direction
Start by reading the DNS Framework API definitions and permission checks for addDnsServer and createDnsZone, then trace how DNS server and zone ownership and public suffixes are handled. The issue proposes several alternative changes, including tenant ownership, domain admin access, and suffix rules, so first agree on scope with maintainers. Done means tenants can manage delegated vanity zones under the agreed ownership and access rules without receiving the PowerDNS API key.
Written by the indexing model from the issue text.
Description
ISSUE TYPE
- Improvement Request / Bug Report
COMPONENT NAME
DNS Framework (PowerDNS provider), API, UI
CLOUDSTACK VERSION
4.23.0.0
SUMMARY
The new DNS Framework works well for provider-owned zones, but in a multi-tenant
cloud there is no way for a tenant to manage a zone for a domain they own
(e.g. customer.com). Every tenant zone is forced under the public server's
suffix, and the admin cannot create a server entry or zone on a tenant's behalf.
OBSERVED BEHAVIOUR
addDnsServercalled by a non-root account fails with
"This API can only be called by root admin".
The documentation states that admins and domain admins can create public
DNS servers, so either the docs or the permission check is wrong.- Only one DNS server entry per account + URL is allowed
("This Account already has a DNS server integration for URL: ..."). addDnsServerandcreateDnsZonehave noaccount,domainidor
projectidparameters (verified withlist apis ... filter=params),
so root cannot create a server entry or zone owned by a tenant.- Zones created by root are owned by root and are not visible to tenants.
- Tenants creating zones on a public server are always restricted to the
singlepublicdomainsuffix.
Result: a tenant who owns customer.com and delegates it to our nameservers
cannot manage that zone through CloudStack. The only workarounds are manual
management by root, a separate DNS UI outside CloudStack, or CNAMEs from the
vanity zone into a suffixed tenant zone.
USE CASE
- Provider runs a PowerDNS cluster and wants to offer managed DNS to tenants.
- Default: tenants self-serve zones under
cloud.provider.example
(works today). - Some tenants own their own domains (
customer.com), delegate them to the
provider's nameservers, and need to manage records (A, MX, TXT, CNAME)
and VM auto-registration for them, without access to the PowerDNS API key.
PROPOSED IMPROVEMENTS
- Add
account+domainid(andprojectid) toaddDnsServerand
createDnsZone, consistent with other CloudStack resource APIs, so root
can provision a server entry or zone owned by a tenant. - Alternatively, an API to change zone ownership
(e.g.assignDnsZone/updateDnsZone account=... domainid=...). - Allow domain admins to call
addDnsServeras documented, or update the
docs if root-only is intended. - Allow multiple allowed suffixes per public server, or per-domain suffix
rules (e.g. domainROOT/CustomerAmay createcustomer.com). - Optional: an ownership verification step (TXT challenge) before a tenant
can create a zone outside the public suffix, to prevent zone squatting.
STEPS TO REPRODUCE
- As root admin, add a public PowerDNS server with
publicdomainsuffix=cloud.provider.example. - As a tenant user, try to create zone
customer.com-> forced under the suffix. - As a tenant user or domain admin, try
addDnsServer-> "can only be called by root admin". - As root, try
addDnsServeragain with the same URL -> "already has a DNS server integration for URL". - As root, create zone
customer.com-> owned by root, not visible to the tenant.
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 7d 4h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/cloudstack
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/cloudstack#14719 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
apache/cloudstack#14715 ·
Maintainers usually reply within 1 day
-
resizeVolume of a running system VM's volume is accepted but the VM never sees the new sizePossibly taken @bhouse-nexthop claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/cloudstack#14645 · 1 comment ·
Maintainers usually reply within 1 day
-
VR reports a load balancer change as applied when haproxy.cfg cannot be replacedPossibly taken @bhouse-nexthop claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/cloudstack#14633 · 1 comment ·
Maintainers usually reply within 1 day
-
restartNetwork reports a ResourceUnavailableException as an unexpected error (530), unlike restartVPC (534)Possibly taken @bhouse-nexthop claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/cloudstack#14631 · 1 comment ·
Maintainers usually reply within 1 day
All issues in apache/cloudstack
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
SAP/ai-sdk-java#1206 ·
Maintainers usually reply within 1 day
-
enhancement good first issue insight-module
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sdlc-pro/spring-lens#606 ·
Maintainers usually reply within 1 day
-
quality-assurance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Paul-Austin-Oswego-CSC480-HCI521/gift-app#252 ·
Maintainers usually reply within 1 day
-
backlog kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
TencentBlueKing/bk-job#4627 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
openrocket/openrocket#3460 ·
Maintainers usually reply within 1 day