Skip to content

DNS zones

Manage local DNS zones and records for hosted domains.

1Overview

DNS manages zones, nameserver records, and customer-owned DNS entries that are available through the panel DNS provider. It is separate from external registrars or third-party DNS providers.

DNS zones in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
DNS Zones and Records page showing authoritative zones, record counts, nameserver settings, and zone management controls.

DNS zones in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Open DNS, select the domain, add or edit the required A, AAAA, CNAME, MX, TXT, or SRV record, and save. Use exact host labels and leave the zone apex blank or use the interface convention when editing the root domain.

  1. Open DNS and choose the exact hosted domain and zone you intend to change.
  2. Check where the domain nameservers point; the zone must be served by the authoritative provider for changes to affect public DNS.
  3. Identify the existing record by name and type, then decide whether it needs editing or a new record.
  4. Enter an A or AAAA address, CNAME destination, MX mail host, or TXT value in the matching form fields.
  5. Use the form guidance for the root-domain label and TTL; enter MX priority when required.
  6. Save one change and reopen the record to verify the stored value.
  7. Review the domain NS and mail records, including SPF, DKIM, and DMARC, without removing unrelated verification records.
  8. If this zone participates in a DNS cluster, check synchronization after saving.

4Practical example

Example: an A record for www.example.com points the www hostname to a server address. An MX record points to a mail hostname, not directly to an email address such as help@example.com.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Reopen the zone and compare the saved record with the requested value.
  2. Query an authoritative nameserver after propagation if external validation is required.

6Common problems and what to check

A public lookup has not changed: confirm the authoritative nameservers, the saved record, and the previous TTL.

A CNAME cannot be saved: check whether other record types already use the same name.

Mail stops after a change: review MX targets and the generated mail-authentication records before making further edits.

7Security, impact, and rollback

Check the authoritative provider before making changes. Incorrect MX, SPF, DKIM, DMARC, or nameserver records can interrupt email and website delivery.

Related guides

DNS ClusterSynchronize eligible local PowerDNS zones to connected DNSOnly targets.DatabasesReview database servers and perform account-scoped database administration.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area