DNS (Domain Name System) is the phone book of the internet. It translates human-friendly names like example.com into IP addresses computers use.
The records you'll actually use
| Record | Purpose | Example |
|---|---|---|
| A | Points a name to an IPv4 address | @ → 203.0.113.10 |
| AAAA | Points a name to an IPv6 address | @ → 2001:db8::1 |
| CNAME | Alias one name to another | www → example.com |
| MX | Where email is delivered | @ → mx1.hostn.me (10) |
| TXT | Verification, SPF, DKIM, DMARC | v=spf1 include:_spf.hostn.me ~all |
Nameservers vs. records
- Nameservers decide who answers DNS questions for your domain.
- Records are the answers themselves.
If your nameservers point to Hostn.ME, edit records in Domains → DNS Zone. If they point elsewhere (e.g. Cloudflare), edit records there instead.
Connecting a domain to your hosting
Type Name Value TTL
A @ <your server IP> 3600
CNAME www yourdomain.com 3600
Why aren't my changes showing?
DNS answers are cached for the record's TTL (time to live). Changes usually appear within minutes but can take up to 24–48 hours worldwide. Check propagation from your terminal:
dig +short yourdomain.com A
nslookup yourdomain.com 8.8.8.8
Tip: Lower the TTL to 300 seconds a day before a planned migration, then switch records. Raise it again afterwards.
Email authentication essentials
To stop your mail landing in spam, add all three:
- SPF – which servers may send for your domain
- DKIM – a cryptographic signature (generated in your email settings)
- DMARC – what receivers should do with failures:
v=DMARC1; p=quarantine; rua=mailto:[email protected]
Stuck on a step?
Our AI assistant knows every tutorial, and a real engineer is one click away.