PROP-INCONSISTENT
Resolvers disagree about this record
What it means
After a DNS change, every resolver keeps the old answer until its cached copy expires (the old TTL). Until then, some visitors see the new value and others the old.
How to fix it
- 1Wait for the old TTL to elapse; nothing else is needed.
- 2Before the next change, lower the TTL a day ahead so propagation is quick.
- 3If a resolver still disagrees long after the TTL, it has a forced or stale cache; nothing on your side fixes that.
Re-check after the change
DNS changes can take up to the record's TTL to be seen; use Re-run on the result page to bypass our 10-minute cache.
