On this page

Last updated: November 19, 2026

DNS Records

The records of a domain hosted on Guara DNS are on its page under DNS in the dashboard. Click Add record to create one, or use the menu on a record to edit or delete it. Project viewers see the records read-only.

Changes reach Guara’s nameservers within seconds. Resolvers that already cached the old answer keep it until its TTL runs out.

Supported types

TypeValueExample
AIPv4 address192.0.2.1
AAAAIPv6 address2001:db8::1
CNAMEAnother hostnameapp.example.net
MXPriority and mail server10 mx.example.net
TXTText (SPF, DKIM, DMARC, verifications)v=spf1 include:_spf.example.net ~all
CAAFlags, tag and value0 issue "letsencrypt.org"
SRVPriority, weight, port and target10 5 5060 sip.example.net
NSA nameserver, to delegate a subdomainns1.other-provider.net

Other types (PTR, DS, TLSA and so on) aren’t supported.

Service records appear when a custom domain of one of your services sits in the domain. They point the name at the service, are locked here, and go away when the custom domain is removed. Guara also manages the domain’s SOA and root NS records itself.

Names

  • @ is the domain itself (example.com.br).
  • Any other name is relative to the domain: www is www.example.com.br. Typing the full name also works.
  • Names may contain letters, digits, hyphens and underscores (_dmarc, selector._domainkey).
  • * as the first label is a wildcard: * answers for any name without records of its own, and *.app for any name under app.
  • Internationalized names (café) are converted to their ASCII form.

Rules

  • A CNAME stands alone. A name with a CNAME can’t have any other record, and the domain itself (@) can’t have a CNAME. To point the root at a Guara service, add it as a custom domain instead.
  • NS records delegate a subdomain (for example dev to another provider). Nothing else can live at or below a delegated name.
  • One TTL per name and type. Records with the same name and type share a TTL; changing it on one changes it on all.
  • TXT values can be up to 4,096 bytes. Long values such as DKIM keys are split into 255-byte strings automatically, so paste them whole.
  • Identical records are refused.

TTL

The TTL is how long resolvers keep an answer, from 1 minute to 1 day. A new record takes the TTL of the other records with its name and type, or 1 hour if it’s the first. Service records use 5 minutes, so a service’s addresses can change quickly.

Lower the TTL a day before a planned change to make it take effect faster, and raise it again afterwards.

Importing a zone file

Most DNS providers can export a domain’s records as a zone file (BIND format). On the domain’s page, click Import, paste the file or choose it (up to 256 KB), then Preview import:

  • To add: the records that will be created.
  • Skipped: records already in the domain, and the source’s SOA and root NS records (Guara manages its own).
  • Rejected: lines Guara can’t import, each with its line number and reason: unsupported types, names outside the domain, records breaking a rule above, or more records than your plan allows.

Nothing changes until you click Import. The file’s $ORIGIN and $TTL are followed; TTLs outside 1 minute to 1 day are adjusted to fit. $INCLUDE and $GENERATE aren’t supported.

Exporting

Click Export above the records to download them as a zone file, ready to import elsewhere or to keep as a backup.

From the terminal

The CLI manages the same records:

guara dns records list example.com.br
guara dns records add example.com.br --type MX --name @ --value "10 mx.example.net"
guara dns records import example.com.br --file old-provider.zone --dry-run