Create or import an owned zone
Open DNS Zone Manager or Customer DNS Zone Editor and select the owning active account. Choose local or external management, full zone name, default TTL and supported template. Local mode manages the panel's authoritative service; external mode records requirements for the actual DNS provider. It does not grant control of an external provider.
Use POST /v1/dns-zones for creation, /v1/dns-zones/import for a reviewed BIND zone file and /v1/dns-zone-templates for a template. Review imported contents before submission. Templates do not transfer ownership or update parent delegation.
Supported record fields
| Type | Required value |
|---|---|
| A | IPv4 address. |
| AAAA | IPv6 address. |
| CNAME | Full target; not permitted at zone apex or alongside another type at the same owner. |
| NS | Full nameserver target; include at least one apex NS. |
| MX | Full mail-server target and priority 0–65535. |
| SRV | Full target, priority/weight 0–65535 and port 1–65535. |
| TXT | 1–8 strings, each 1–255 UTF-8 bytes without control characters. |
| CAA | Flags 0–255, lowercase tag of 1–15 letters/digits and value up to 255 bytes. |
Record name is the complete zone apex or a complete name beneath it. TTL is 60–604800 seconds. Up to 256 managed records are reviewed per zone. NS/MX/SRV targets cannot be CNAMEs, and CNAME cycles are rejected. The SOA editor includes primary nameserver, responsible mailbox, refresh, retry, expire and negative-cache TTL; use its supported domain-style mailbox encoding.
Edit, export and verify
Modification uses current zone revision and the reviewed complete record set. Export uses GET /v1/dns-zones/{id}/export. Diagnostics and explicit verification inspect different authority/delegation evidence; refresh them after changes and inspect their timestamps. Pending external DNS stays pending until independently verified.
DNSSEC status and DS guidance belong to the actual signed-zone workflow. A key-rotation route exists at /v1/dns-zones/{id}/dnssec/rotate; availability depends on the installed capability and protection checks. Registrar DS/glue/delegation changes require your actual registrar. Panel contains no registrar purchase, renewal or transfer drivers, and DNS synchronization/clustering is outside this single-server architecture.
Verify publicly and recover carefully
Test both UDP and TCP port 53, intended nameservers, parent delegation and external answers. Two nameserver labels on one VM are not two failure domains. A local zone file or successful resolver cache does not prove authority. The candidate retains a separate unresolved first-DNS-create recovery/install boundary; preserve blocked original operations and do not remove activation gates, requeue SQL manually or rerun creation under a new ID to hide failure. Dynamic DNS is not implemented.