Common DNS Record Types
| Type | Purpose | Example |
|---|---|---|
| A | Maps a domain to an IPv4 address | example.com → 93.184.216.34 |
| AAAA | Maps a domain to an IPv6 address | example.com → 2606:2800::1 |
| MX | Specifies mail servers for a domain | example.com → mail.example.com (priority 10) |
| CNAME | Aliases one domain to another | www.example.com → example.com |
| TXT | Arbitrary text, used for SPF, DKIM, and verification | v=spf1 include:_spf.google.com ~all |
| NS | Authoritative nameservers for the domain | ns1.example.com, ns2.example.com |
| SOA | Start of Authority — zone metadata and serial number | Primary NS, admin email, refresh intervals |
How to Use DNS Propagation Check
When you update a DNS record, the change doesn't instantly reach every resolver worldwide. Resolvers cache records for the duration of the TTL (Time to Live) value, which can range from 60 seconds to 86400 seconds (24 hours). Until the TTL expires, different users around the world may see different values for the same domain.
The propagation checker queries multiple public resolvers simultaneously and shows you whether they all agree. If some resolvers show your old value and others show the new one, propagation is still in progress. Once all resolvers agree, propagation is complete.
To speed up propagation before making a planned change, lower your TTL to 300 (5 minutes) a few hours beforehand. After the change is live and stable, raise it back to 3600 or higher.