Overview
The Xloud DNS service uses a multi-tier architecture separating the API layer, the central processing service, and the backend DNS server pools. This separation allows the management plane to scale independently from the data plane that serves resolver queries.Service Topology
The DNS API and central service operate in the management plane. Nameservers in
pools operate as data-plane components — they respond to resolver queries directly
without routing through the API layer.
Component Descriptions
| Component | Role | Port |
|---|---|---|
| DNS API | REST API for zone and record management | 9001 |
| DNS Central | Orchestrates zone lifecycle, writes to the database | Internal |
| DNS Worker | Pushes zone data to backend nameserver pools | Internal |
| Message Queue | Decouples Central from Workers for async processing | Internal |
| Service Database | Stores zone metadata, record sets, and pool configuration | Internal |
| Nameserver Pool | Backend DNS servers that answer resolver queries | 53 (UDP/TCP) |
Request Flow
Zone Creation
High Availability
The DNS management plane components (API, Central, Worker) are deployed as containerized services managed by XDeploy. For production deployments:- Deploy at least two API containers behind a load balancer
- Run two Worker instances for redundancy — only one processes each event (queue-based)
- Database and message queue are shared, managed services
The data plane (nameservers) operates independently of the management plane. Resolver
queries continue to be served even if the DNS API or central service is temporarily
unavailable. Only zone updates and record changes require the management plane.
Next Steps
Backend Configuration
Configure backend DNS drivers and pool targets
Pool Management
Manage nameserver pools and geographic distribution
Security
Harden the DNS service and protect zone data
Troubleshooting
Diagnose and resolve platform-level DNS issues