Skip to main content

​
Overview

DNS quotas prevent individual projects from consuming excessive DNS resources. Default values are set platform-wide; administrators override them per project. Quota enforcement is automatic — operations that would exceed a limit return a 413 or 429 error.
Administrator Access Required — This operation requires the admin role. Contact your Xloud administrator if you do not have sufficient permissions.

​
Default Quota Reference

ResourceDefault LimitDescription
zones10DNS zones per project
zone_records500Total records across all zones in a project
zone_recordsets500Total record sets across all zones
recordset_records20Records within a single record set
ptr_records30PTR records per project

​
View Quotas

Show quotas for the current project
openstack quota show --dns

​
Set Quotas

Set DNS quotas for a project
openstack quota set \
  --dns-zones 50 \
  --dns-zone-records 2000 \
  --dns-zone-recordsets 2000 \
  --dns-recordset-records 50 \
  <project-id>
Reset to platform defaults
openstack quota delete <project-id> --dns
Large projects with automated DNS management (e.g., service-discovery-heavy environments) may need zone_recordsets quotas in the thousands. Review usage regularly and right-size allocations based on actual consumption.

​
Monitor Quota Usage

Check current usage against limits before planning quota changes:
Show zone count for a project
openstack zone list --project <project-id> -c name | wc -l
Count total record sets across all zones
for zone in $(openstack zone list --project <project-id> -f value -c name); do
  openstack recordset list "$zone" -f value -c name
done | wc -l

​
Next Steps

Pool Management

Manage nameserver infrastructure that processes zone data

Security

Apply DNS security hardening policies

Admin Troubleshooting

Diagnose quota-related errors and service issues

DNS User Guide

User-facing zone and record management