DNS (Domain Name System) is the internet's address book. It translates domain names like yourstore.com to IP addresses that computers understand. When you change DNS records, these changes need to spread throughout the internet — this is called DNS propagation.
How does DNS work?
When someone enters your web address in a browser, the following happens:
The browser asks a DNS resolver
Your ISP's DNS server receives the question: "What IP address does yourstore.com have?"
The resolver searches for the answer
If the answer isn't in cache, the resolver asks root nameservers, then TLD servers (.com), and finally your domain's nameserver.
The answer is cached
The answer is stored in cache for a certain time (TTL — Time To Live) so the same question doesn't need to be asked again.
The browser connects
With the IP address, the browser can connect to the right server and display your website.
Common DNS record types
| Typ | Namn | Värde / Pekar på | TTL |
|---|---|---|---|
| A | @ | 76.76.21.21 | 3600 |
| AAAA | @ | 2001:db8::1 | 3600 |
| CNAME | www | cname.vercel-dns.com | 3600 |
| TXT | @ | v=spf1 include:... | 3600 |
| MX | @ | mail.provider.com | 3600 |
A record — Points the domain to an IPv4 address. Used for the root domain (e.g. yourstore.com).
AAAA record — Same as A but for IPv6 addresses.
CNAME record — Points a name to another name. Often used for the www version of the domain.
TXT record — Text record used for verification, SPF, DKIM, and other purposes.
MX record — Points the domain's email to a specific mail server.
What is DNS propagation?
When you change a DNS record, it's first updated at your domain provider's nameserver. But DNS resolvers worldwide often have the old record cached. It takes time for all caches to update with the new information.
Typical propagation times
5–30 min
Most changes
1–4 h
Complex changes
24–48 h
Maximum global spread
Tips for faster propagation
- 1Lower TTL in advance — Change TTL to a low value (60–300 seconds) at least 24 hours before you plan to change DNS records.
- 2Flush local DNS cache — Run
ipconfig /flushdns(Windows) orsudo dscacheutil -flushcache(Mac). - 3Test with different DNS — Try Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) to see if propagation has reached there.
Be patient
During propagation, your website may work for some visitors but not others. This is normal and resolves once all DNS servers have been updated. Avoid making further changes during propagation.
Troubleshooting
Domain points to wrong location
Double-check that A and CNAME records are correct. Remove any old records that may conflict.
"DNS_PROBE_FINISHED_NXDOMAIN"
The domain cannot be found at all. Check that the nameserver is correctly configured and that the domain hasn't expired.
Works on mobile but not desktop (or vice versa)
Different devices may use different DNS resolvers. Wait for propagation to complete or flush the device's DNS cache.