Stale MX Record Cache on OpenDNS Resolver

[NormNL]

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:

• Date of MX Record Change: June 8th
• Registrar / Host: GoDaddy
• Email Provider: Google Workspace
• Current TTL for MX Records: initially 1hr, today changed to 12hrs

Troubleshooting Steps Taken:

1. We have confirmed with our host (GoDaddy) that the new DNS records are published correctly from their end.
2. We have confirmed with Google that our DNS settings are correct according to their tools.
3. We have been monitoring propagation on DNSchecker.org and other tools for over 7 days, which consistently show the old record on a small number of servers, including the OpenDNS server at 208.67.222.220

Thank you for your support.
Norman

[Jonatan Jonasson]

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.