UAPP DNS
Manage account-owned DNS zones, address choices, nameservers, mail policies and records in UAPP with export and safe editing requirements.
Open Hosting → DNS. The DNS feature must be enabled for the signed-in hosting account.
| Menu or workflow | Purpose |
|---|---|
| DNS Zones | Inspect owned zones, nameservers, templates and mail policies. |
| Add DNS Zone | Create a zone using an available template and IPv4/IPv6 choices. |
| DNS Records | Open a zone's manager to add/edit/delete records, migrate legacy data or download the zone. |
| Add DNS Records | Follow the form step by step, including Name, target, TTL and save validation. |
| Common Record Examples | Fill A, AAAA, CNAME, MX, TXT, NS, SRV and CAA fields. |
| Advanced Record Fields | Fill the other 11 supported types, including TLSA, DS, NAPTR, RP, SVCB and HTTPS. |
DNS Records is a workflow reached from DNS Zones, not an additional fixed sidebar menu. Templates are selected from available definitions; UAPP has no separate template-authoring menu in this group.
Scope and prerequisites
Zone management checks the signed-in account's ownership. A known domain or website URL alone does not grant DNS access. DNS zones and website configurations are separate resources: creating a zone does not register a domain or create a website, mailbox or database.
Changes here affect this server's zone configuration. If public DNS is hosted elsewhere, update that authoritative provider as appropriate. Registrar delegation and nameserver glue are separate from a zone's NS records.
Preserve working DNS before changes
Record the current settings or download a supported export before substantial changes. Incorrect web, mail, delegation or certificate-validation records can interrupt services. Check actual authoritative answers and affected services after saving.
Demo mode blocks creation and record mutations; policy, nameserver and template helpers also reject demo writes. Deletion checks both ownership and whether a hosted website still uses the zone. Backend permissions and record validation remain authoritative even when an action is visible.