Why does it take a while for domain changes to be verified?
You published a DNS record and ClearDMARC is still showing it as unverified. This is almost always normal. Here is why propagation takes time, and what you can do about it.
How DNS propagation works
The global DNS system is not a single database. It is a hierarchy of caches. When you publish or change a record at your registrar or DNS provider, that change is immediately live at your authoritative nameservers. However, every resolver worldwide that has recently queried your domain holds a cached copy of the old answer. It will not discard it until the record’s TTL (Time to Live) expires.
What TTL means in practice
| TTL value | Max wait time | Typical use |
|---|---|---|
| 300 s (5 min) | ~5 minutes | Managed services, low-TTL records |
| 3600 s (1 hr) | ~1 hour | Common default for TXT/SPF |
| 86400 s (24 hr) | Up to 48 hours | Default at some legacy DNS providers |
ClearDMARC verifies your records from multiple independent resolvers across regions. The check shows Verified only once all vantage points agree. That means it can take as long as the highest TTL any resolver had cached.
How to speed things up
- Lower your TTL before making changes. If you know a DNS change is coming, reduce the record’s TTL to 300 seconds a day in advance. Resolvers will then re-query within 5 minutes of your change going live.
- Use ClearAuth managed services. ClearDKIM keeps your keys in a dedicated DNS zone for your domain, on AWS Route 53, with a 5-minute TTL, so key changes reach receivers in minutes. With ClearSPF you change senders in the console, not in your DNS: the managed record updates when you save, and receivers re-read it at least once an hour.
- Check from the authoritative source first. The Tools page in ClearDMARC lets you query your authoritative nameserver directly to confirm the record is published, before global resolvers have caught up.
Why ClearDMARC checks multiple vantage points
Receiving mail servers around the world query DNS independently. A record that looks correct from your location or from Google’s 8.8.8.8 resolver might still be stale at a resolver in another region. By verifying from multiple locations, ClearDMARC confirms that your change is live everywhere, not just where you happen to be querying from.
Double-check that the record was saved at your DNS provider (not just previewed), that there are no typos in the value, and that you do not have a conflicting record of the same type for the same name. Contact support if the problem persists.