--- title: "Records" description: "Add and edit DNS records: every supported type, what the name field means, and how to pick a TTL that makes changes propagate when you need them to." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/dns-records updated: 2026-11-17 --- # Records Open the zone → **DNS Records** tab in [my.cubepath.com](https://my.cubepath.com). ![DNS records of a zone: apex group with A, AAAA, MX, TXT, plus www and mail](https://cdn.cubepath.com/img/docs/products/3bbd1e23-6ab8-4e2d-9940-041caa0b7365.png) Records are the zone's actual content: the answers our nameservers give when a resolver asks about a name under your domain. Everything else in a DNS zone (regions, health checks, SOA timers) only shapes *how* these answers are served. ## Add a record ```steps ### Click Add Record The dialog opens with the most common combination already selected: an **A** record on `@`. ### Set the name `@` is the domain itself (`example.com`). Anything else is a subdomain: `www`, `api`, `mail`. Don't type the domain again: `www` becomes `www.example.com`. ### Pick the type and value The placeholder in the **Content** field shows the shape the type expects. ### Set the TTL Seconds. 60 is a sensible default and the lowest the form accepts; lower floors come with the higher plans. ### Save The record is live within seconds; resolvers that already cached an older answer keep serving it until its TTL expires. ``` ## Record types | Type | What it's for | |------|---------------| | **A** | An IPv4 address. The one you'll add most | | **AAAA** | An IPv6 address | | **CNAME** | An alias pointing at another name. Not valid on `@` | | **ALIAS** | An alias at the apex (`@`): what you use when a CNAME would be illegal there | | **MX** | Mail exchange. Needs a **priority**; lower wins | | **TXT** | Free text. SPF, DKIM, DMARC and domain-ownership tokens all live here | | **SRV** | A service endpoint. Needs **priority**, **weight** and **port** | | **CAA** | Which certificate authorities may issue for the domain | | **NS** | Delegates a subdomain to someone else's nameservers | | **PTR** | Pointer record, for reverse lookups | | **SSHFP** | SSH host key fingerprint | | **TLSA** | Pins a TLS certificate for DANE | The dialog only shows the extra fields a type actually needs, so **Priority** appears for MX and SRV, and **Weight** and **Port** for SRV alone. ## TTL TTL is how many seconds a resolver may cache the answer before asking again. It's the single setting with the most operational consequence in DNS, because it decides how long a mistake (or a planned change) takes to disappear from the internet. - **Low (30–60 s)** for anything that moves: records with [health checks](/docs/products/deployment/dns-health-checks), records you're about to change, anything failing over. - **Higher (hours)** for records that never change: MX, TXT verification tokens, a CNAME to a CDN. > Tip: Drop the TTL on a record **a day before** you plan to change it, not at the same time. Resolvers cached the old value with the old TTL; lowering it now doesn't shorten a cache entry that already exists. ## Comments and system records Every record takes an optional **comment** (up to 255 characters). Use it: six months later, "temporary, remove after the migration" is the difference between deleting a record confidently and leaving it forever. Some records are managed by the system and can't be renamed. They're there because the zone needs them to function. ## Editing and deleting Editing a record replaces the answer; the change takes effect as soon as it's saved and resolvers stop serving the old one when their cached copy expires. Deleting is immediate and the confirmation dialog is the only safeguard, so read the name before you confirm: deleting the `@` A record takes the site offline. ## Related - Serving different values by region: [GeoDNS](/docs/products/deployment/dns-geodns). - Removing a dead address from the answers automatically: [Health checks](/docs/products/deployment/dns-health-checks). - SPF, DKIM and DMARC without hand-writing the TXT records: [Recommendations](/docs/products/deployment/dns-email-security).