06-16-2025 09:10 AM
Hello OpenDNS Community and Support,
I'm writing to request assistance with a persistent DNS caching issue for our domain. We updated our MX records over a week ago, and while the change has propagated successfully across most of the internet, it appears to be stuck on at least one OpenDNS resolver at IP 208.67.222.220
Here are the relevant details:
Troubleshooting Steps Taken:
Thank you for your support.
Norman
06-16-2025 05:14 PM
Was the serial number of the domain increased?
Have you tried increasing the serial +1 again, just for the fun of it?
Potential glue record mismatch?
What I would do in your scenario, is to head over to Umbrella support - https://support.umbrella.com/hc/en-us
In the top right corner there's a "submit a request" button, and it appears you don't even have to be logged in to use it.
There you can send in your request and provide information that you might not want to share in a public forum (your domain name, name servers, etc.)
And then you can get more direct assistance on your issue.
09-26-2025 06:33 AM
I have a similar issue. Did some DNS changes more than 20 days ago, and on cachecheck.opendns.org it still shows as NO_RECORD for several cache servers. If I "dig" through Google's DNS, Cloudflare's DNS or any other DNS I get the correct records, it's only on OpenDNS that they seem to not have propagated.
I'm getting bounced emails from customers with "domain unavailable" and SPF errors because of this. Wix and Google have already reviewed and it's all properly setup on their side.
Domain is www.construagil.com.br
I tried forcing the update on the cache check website, to no avail. Does anyone have any ideas I could try? The "Open support ticket" option is no more after Umbrella's transition to Cisco
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide