Skip to Content
Browse documentation

Manage RAPP DNS Records

Edit account-scoped DNS records with type-specific fields, TTL validation, automatic SOA serials, legacy conversion and stale-revision protection.

From DNS Zones, open the intended domain's record manager. Confirm domain, owner and template. Demo sessions and suspended reseller/account contexts are read-only.

Standard record fields

The table shows record type, name, content, TTL and actions. Type, Name, applicable Content and TTL are required. Use @ for the zone apex or a relative name such as www. Enter a type-appropriate address, target or value. TTL is seconds, with the visible range 0–2147483647; server DNS validation also applies.

Supported types: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, TLSA, PTR, SOA, AFSDB, DNAME, DS, HINFO, LOC, NAPTR, RP, SVCB and HTTPS. TXT uses its text editor; do not treat all content as an IP address.

Type-specific fields

TypeAdditional information
MXPriority and mail-server target.
SRVPriority, weight, port and service target.
CAAFlags, tag and policy value.
TLSAUsage, selector, matching type and certificate association data.
AFSDBSubtype and server target.
DSKey tag, algorithm, digest type and digest.
HINFOCPU description and operating system.
NAPTROrder, preference, flags, service, regular expression and replacement.
RPResponsible mailbox and TXT domain.
SVCB / HTTPSPriority, service target and optional service parameters. Alias priority zero has no parameters; service mode uses priority one or higher.
LOCLocation coordinates.
SOAPrimary nameserver, responsible mailbox, refresh, retry, expire and displayed serial/minimum metadata.

The SOA serial is managed automatically, and displayed serial/minimum controls are read-only. SOA has no normal delete action. Type-specific ranges and relationships are validated by the DNS service, beyond the broad numeric controls shown in the form. Use mailbox/email syntax where the field requests it.

Add, edit and delete

Open Add or Edit, complete the fields relevant to the chosen type and save. Deleting opens a confirmation showing name, type and value; inspect all three before confirming. Copies from the content control are for reference, not changes.

Writes carry the loaded zone revision. If another update makes your view stale, refresh and reconcile the current records rather than repeatedly submitting old values. A legacy-zone notice can require explicit migration before editing; review the zone and any validation feedback before converting.

ACME challenge data is shown separately from ordinary editable records. Preserve certificate-validation behavior and do not replace DNS record or challenge handling merely to remove a display warning.

Check record relationships

An individually valid record can still conflict with aliases, apex requirements or another service's expectations. Review the whole zone, save response and authoritative answers, then verify affected web/mail/certificate behavior.