DNS Propagation

You've added the DNS records. The domain isn't working yet. This is DNS propagation — the time it takes for your changes to spread across the global DNS system. Here is what is happening and what to expect.

---

How the DNS System Works

The Domain Name System (DNS) is a distributed global database that translates human-readable domain names (go.yourbrand.com) into IP addresses (198.51.100.42) that servers use to route internet traffic. When a browser needs to connect to a domain, it queries a DNS resolver — typically provided by the ISP or a public service like Google (8.8.8.8) or Cloudflare (1.1.1.1) — which looks up the domain's current DNS records.

The DNS system is hierarchical and heavily cached:

1. Authoritative DNS server. The source of truth for a domain's records — typically your domain registrar or a managed DNS service. When you add an A record or TXT record, you are updating the authoritative server immediately.
2. DNS resolvers. Intermediate servers that cache DNS records to speed up lookups. When a resolver receives a query for a domain, it checks its cache — if it has a recent record, it returns the cached value without querying the authoritative server.
3. Cache TTL (Time to Live). Each DNS record includes a TTL value — the number of seconds resolvers should cache the record before re-querying the authoritative server. A TTL of 3600 means resolvers cache the record for up to one hour before checking for updates.

What DNS Propagation Actually Is

When you update a DNS record, the authoritative server is updated immediately. But DNS resolvers worldwide have cached the old record — and they will continue serving the old cached value until their TTL expires and they re-query the authoritative server.

DNS propagation is the process of cached records expiring and resolvers refreshing with the new values across the global DNS network. During propagation, different users in different locations — querying different DNS resolvers with different cache states — may get different answers for the same domain query. One user sees the domain working; another gets an error or the old destination.

DNS Records Required for Cuttly Custom Domain Setup

Connecting a custom domain to Cuttly requires two DNS records:

Important: Cuttly uses A record + TXT record for custom domain configuration — not a CNAME record. CNAME records cannot be used on root/apex domains (e.g. yourdomain.com) per DNS standards — only A records can be used at the apex. For subdomains (go.yourdomain.com), both A records and CNAMEs are technically possible, but Cuttly's setup requires the A record approach.

How Long Does Propagation Take?

Propagation time depends on the TTL of the records being changed and the cache states of DNS resolvers worldwide:

The 48-hour figure often cited is the theoretical maximum based on historical TTL configurations — in practice, most propagation completes within 2–8 hours because most modern DNS resolvers use shorter cache times than the maximum TTL allows.

How to Check Propagation Status

Several tools allow you to check the current DNS record values being returned by resolvers in different geographic locations:

• whatsmydns.net — checks A record, TXT record and other record types across dozens of resolvers globally, showing which locations have the new record and which are still returning old cached values
• dnschecker.org — similar multi-location DNS lookup tool
• Google Admin Toolbox Dig (toolbox.googleapps.com/apps/dig/) — DNS lookup tool useful for checking specific record types
• Terminal / command line: dig go.yourdomain.com A or nslookup go.yourdomain.com — checks the record as seen from your current network's resolver

Check TXT record propagation specifically with: dig TXT go.yourdomain.com — this shows whether the verification token is visible to resolvers, which Cuttly queries to confirm domain ownership.

Common Issues During Propagation

• "The domain isn't working on my computer but works on my phone." Your computer and phone may be using different DNS resolvers with different cache states. This is normal during propagation — both will resolve correctly once their respective resolvers refresh.
• "I added the records hours ago but Cuttly still can't verify the domain." Cuttly checks for the TXT verification record from its own servers using its own resolver. If that resolver's cache hasn't refreshed yet, verification will fail. Wait and retry — do not add the records again. Adding duplicate records can cause validation issues.
• "The records look correct in my DNS provider's interface but the domain doesn't resolve." Check that records were saved correctly. Some DNS providers require explicit saving after adding records; others apply changes immediately. Use whatsmydns.net to verify the records are publicly visible — not just visible in your provider's interface.

Reducing Propagation Time

If you need a domain to propagate as quickly as possible — for example, when preparing a custom domain for an imminent campaign launch — reduce the domain's TTL before making DNS changes. Set the TTL to a low value (300 seconds = 5 minutes) 24–48 hours before you plan to make the change. When resolvers re-query within 5 minutes, they refresh with the new record rapidly. After propagation completes, TTL can be returned to a normal value (3600 seconds).

Related Terms

• Custom Domain
• HTTPS & SSL
• Branded Links
• HSTS