Query each authoritative nameserver for the domain’s MX records, then compare those answers with results from multiple recursive resolvers. The authoritative servers show what the DNS zone publishes; recursive resolvers show what their caches currently return. If authorities agree on the new records while some resolvers return older ones, caching is a likely explanation.
What “MX propagation” means
There is no single central update moving through the internet. First, the domain’s authoritative nameservers must publish the intended MX records. Then recursive resolvers used by networks and devices must return the new data instead of an older cached answer. Those two checks answer different questions, and recursive caches refresh independently.
As an Amazon Associate I earn from qualifying purchases.
An MX record identifies a mail destination. Its preference number and exchanger hostname should match the configuration supplied by your mail provider. A successful DNS lookup confirms what the queried server returned; it does not prove that mail delivery works end to end, since server availability, authentication and provider-side settings are separate.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Check the authoritative MX records
- Find the authoritative nameservers. Get them from your DNS provider’s zone details or perform an NS lookup for the domain. Query every listed nameserver: one server publishing different data from the others is not the same problem as recursive-cache lag.
- Query each nameserver for MX. Replace the example names with your domain and an authoritative server:
dig @<authoritative-nameserver> example.com MX - Inspect the answer. Record the MX preference numbers and exchanger hostnames. Compare both values with the intended configuration—not just a lookup tool’s green or red status.
MX is the DNS record type used to identify a domain’s mail destination. Cloudflare’s MX record explainer describes the record’s role.
#1 Best Overall
Compare answers from recursive resolvers
Recursive resolvers are the caching DNS servers that clients commonly rely on. Query more than one public resolver, and, if you are investigating a particular mail problem, check the resolver used by the affected network too.
dig @1.1.1.1 example.com MXdig @8.8.8.8 example.com MX
Compare the full MX set and preferences returned by each resolver with the authoritative answers. If all queried authorities agree on the new values but a recursive resolver still returns the old values, a cached answer is a likely cause. A multi-resolver website can help sample views, but it only reports the resolvers it queries; no finite checker establishes what every network sees. For example, nslookup.io describes its checker as querying more than 30 resolvers across six continents; that is the tool’s stated coverage, not a census of the internet.
Use TTLs to interpret a mismatch
TTL (time to live) indicates the cache lifetime associated with a DNS record. A resolver may have stored the old MX answer before the change and continue to return it until that cached entry expires. Lowering the TTL on the new record after making a change does not retroactively shorten the lifetime of an older answer already in a resolver’s cache. Check the TTL shown in the response and allow for resolvers to refresh independently; there is no universal completion time that applies to every resolver.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If the MX answer is missing
If a resolver returns no MX record, consider whether it cached an earlier negative response—an answer indicating that the name or requested data was absent. Negative caching follows SOA-related rules; Cloudflare’s guidance identifies the zone’s SOA MINIMUM field under RFC 2308 as relevant to the duration.
Cloudflare’s SOA record guidance explains the SOA fields used in DNS zones. For the standard, see RFC 2308.
If old answers persist beyond the expected cache window
A stale answer does not always mean a resolver is counting down a normal, healthy cache entry. RFC 8767 defines a mechanism for resolvers to serve stale data to clients when they cannot refresh it from authoritative servers. If the mismatch persists, check whether the affected resolver can reach the authorities and whether all authoritative nameservers still publish the same MX set. The RFC’s abstract states: “This document defines a method for DNS resolvers to serve stale data to clients.” RFC 8767.
Rank #4
Choose a check that answers the right question
| Check | What it tells you | Best use |
|---|---|---|
| Direct query to each authoritative nameserver | What each authority currently publishes for the domain | Confirm the zone has the intended MX records and authorities agree |
| Query to a named recursive resolver | What that resolver currently returns from its cache or refresh | Reproduce a result from a particular network or resolver |
| Multi-resolver online checker | A sample of answers from the resolvers the checker queries | Conveniently spot differences among sampled views |
Prefer a check that displays full MX values and TTLs rather than only a summary status. A named resolver query is reproducible; a checker is convenient for sampling, but cannot establish universal agreement. For background on the distinction between authoritative data, resolver caches and TTLs, see Cloudflare’s DNS overview.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
