Skip to Content
Browse documentation

Manage UAPP DNS Zones

Review owned DNS zones, change nameservers and templates, toggle SPF DKIM DMARC, view public DKIM records and understand website deletion dependencies.

Open Hosting → DNS → DNS Zones.

To add an individual DNS record, open Manage DNS for the domain and click Add Record. See Add DNS Records for the full form instructions; this differs from creating a new zone.

The list identifies the zone and shows stored IPv4/IPv6 values, nameservers, template and mail-policy states. Templates can come from the default, provider-custom or account-custom scope. These values describe stored configuration, not live resolver or mail-delivery tests.

Actions and fields

ActionFields and behavior
Manage DNSOpens the record editor for the selected owned zone.
Change NameserversSelected zone and at least one valid nameserver hostname. The dialog presents nameserver inputs; the server normalizes and deduplicates entries.
Change DNS TemplateSelected zone and an available template. The server rejects unavailable definitions.
SPF / DKIM / DMARCOn/off policy controls for the selected zone.
View DKIMAvailable when DKIM is enabled; displays public TXT records found under a selector's _domainkey name.
DeleteOffered only when the zone is not associated with a hosted website.

Review the exact domain and intended value before saving. Refresh the row after success and verify authoritative answers. Domain names are normalized and displayed readably for internationalized names.

Changing zone nameservers does not update registrar delegation or create required nameserver glue. Template changes can affect generated zone output; inspect records and policy after changing the selection rather than assuming custom records are unchanged.

Mail-policy controls

SPF, DKIM and DMARC switches request the corresponding DNS policy configuration. They are not a complete external-mail-provider setup, and enabling a policy alone does not establish successful signing, alignment or delivery.

The DKIM viewer reads public selector TXT records from the current version-two zone. A missing result or a legacy zone is not proof that no external authoritative provider publishes a DKIM record. It does not display the signing private key.

Deletion restrictions

The server rejects deletion while the domain remains in this account's hosted-domain collection. Do not remove a live website merely to bypass the DNS restriction; decide deliberately whether the website and zone should be retired.

Removing a zone affects more than its website

Mail, service discovery, certificate validation and other applications may depend on the zone even when no website is listed. Preserve required records and arrange replacement authoritative service before deletion.

Ownership, feature and demo checks apply to mutations. Review failures before retrying and use Add DNS Zone for a new independent zone.