Editing DNS records

Records are edited from inside a zone. Every change publishes to all four nameservers when you save it.

The fields

• Name — the part in front of the domain. @ is the domain itself; www is www.example.com. You do not type the domain again.
• Type — A, AAAA, CNAME, MX, TXT and the rest. See Record types.
• Value — what the record points at. What goes here depends entirely on the type.
• TTL — how long resolvers may cache this answer. See SOA and TTL.

Comments

A record can carry a comment. It is not part of DNS and is never published — it is for you, six months later, wondering what that TXT record was for. Use it on anything that is not self-explanatory, which is most TXT records.

Disabling a record

A record can be disabled rather than deleted. It stays in the zone, keeps its value and its comment, and stops being answered.

This is the right tool for "I think this is unused but I am not certain". Delete removes it; disable lets you put it back in one click when something breaks two days later.

Deleting

Deleting takes the record out of the zone. There is no per-record undo — but the whole zone is versioned, so Time Machine can put it back if your plan includes history.

Things that catch people

• A CNAME cannot sit at the apex. example.com itself cannot be a CNAME; that is a rule of DNS, not of this portal. Growth and above include ALIAS, which does the same job where CNAME is not allowed.
• A CNAME cannot coexist with other records of the same name.
• MX values need a priority, and the target must be a hostname rather than an IP address.
• TXT values with spaces need quoting, and a long SPF or DKIM value is easy to truncate on a copy and paste. Check the saved value, not the one in your clipboard.

Record limits

Your plan sets a maximum number of records per zone. It is counted per zone rather than across the account.

Last reviewed 2026-08-19.