DNS records
A, AAAA, CNAME, MX, TXT — and what to use them for.
If you use Suzko's nameservers, manage DNS at /dashboard/domains → your domain → DNS.
Record types you'll actually use
| Type | What it does | Example value |
|---|---|---|
| A | Point a hostname at an IPv4 | 192.0.2.1 |
| AAAA | Point a hostname at an IPv6 | 2001:db8::1 |
| CNAME | Alias one hostname to another | myapp.deploy.suzko.net. |
| MX | Mail server for the domain | 10 mx.example.com. |
| TXT | Arbitrary string (SPF, DKIM, verification) | v=spf1 include:_spf.example.com ~all |
| NS | Subdomain nameservers | ns1.somewhere.com. |
| SRV | Service location (rare) | 0 5 5060 sip.example.com. |
| CAA | Limit who can issue SSL certs | 0 issue "letsencrypt.org" |
Common setups
Point your apex (yourdomain.com) at Suzko hosting:
- Add an A record, host
@, value = the IP shown on your hosting service page
Point www at the same thing:
- Add a CNAME, host
www, valueyourdomain.com.(trailing dot) - Or a second A record
Point a subdomain at a Deploy project:
- Add a CNAME, host
app, value = the deploy URL (e.g.your-project.apps.suzko.net.)
Email via Business Email:
- We auto-add the MX/SPF/DKIM/DMARC set when you attach a domain to a mailbox. See Business Email DNS setup.
TTL
Time-to-live. How long resolvers cache the record. Default 1 hour is fine for most things. Drop to 5 minutes (300) before a planned change, raise back to 3600+ after the change settles.
Propagation
Changes go live at our nameservers immediately. Recursive DNS resolvers (your ISP, Google DNS, Cloudflare DNS) cache for the TTL window — so it can take up to that long to see the change globally. Most propagate in minutes.
Imported records on transfer
If you transfer a domain in from another registrar, DNS records at their DNS service don't follow. Before flipping nameservers, set up the same records at Suzko.