Troubleshooting
A change applied but is not resolving
My change says applied but the record is not live. Why?
Applied and live are different states in DNSMentor and it will not merge them. Applied means the provider accepted the write. Live means an independent query from outside confirmed it. The gap is usually caching, but occasionally the provider accepted a change it has not served.
# Check the TTL of the old record first
Resolvers that already answered hold the previous value for its full TTL. If the old record had a TTL of 3600 you will see mixed answers for up to an hour, and nothing is wrong.
# When it is not caching
- Some providers need an explicit zone refresh after a write. OVHcloud is the notable one — without the refresh the change is stored and never served.
- A record at the wrong name resolves for nobody and looks correct in the estate view. Run the misplaced-record scanner.
- A CNAME at the apex can cause resolvers to ignore other records at that name, so an unrelated record appears to vanish.
DNSMentor re-verifies on a schedule after apply, so a change that goes live later flips to verified on its own without you doing anything.
Thanks — noted.
Related
Raise a ticket from inside the platform and your tenant, plan and recent activity come attached automatically. A client currently offline is treated as urgent on every plan.