Very slow name server update propagation through OpenDNS

[msmithers]

Hi,

Is there any way to force openDNS to refresh name servers for a domain? I've already opened a support ticket.

3 days ago I changed hosting, and consequently name servers, for a website we manage and we can't get to the site from home - which uses OpenDNS for filtering for the kids. I can change DNS to google on my PC, but my wife makes most of the website changes and her PC - a Toshiba - doesn't allow access to the network settings.

Cheers,

Michael

[msmithers]

I just read a post from someone else who had the same problem and OpenDNS took 5.5 days to refresh name servers!!!! OpenDNS, are you listening?

[rotblitz]

If you want more reliable response from OpenDNS staff, you have to raise a ticket, see link "Submit a request" above.
They don't listen so much here in the community forum which is merely for user-to-user assistance.

But you don't have to wait for OpenDNS staff.
You can refresh the cache for your domains yourself immediately here: https://cachecheck.opendns.com/
(At the end of the page there will appear a button to refresh the cache.)

"I just read a post from someone else who had the same problem"

Really?  Can you post a link to this thread?  People (users) may have missed to point out what to do, unlike here.

Still having problems with resolving your domain names through OpenDNS?  It would be better you told us these domain names, so that someone else can look deeper into the issue.  There are a bunch of DNS experts here, and almost OpenDNS' system is not the culprit, unlike you assume.

[msmithers]

I already raised a support request; see above.

Good suggestion re the cache check link. I had already tried that a day ago and it showed the correct address everywhere except that Australia (where I am) showed "NO RESPONSE." Just now I tried the "refresh" button and Australia was still "NO RESPONSE."

[msmithers]

The domain is southerlychange.net.

[msmithers]

Here's the link you requested.

https://support.opendns.com/hc/en-us/community/posts/220050627-Slow-propagation-of-name-server-change

[msmithers]

It looks like the "Refresh" at the bottom of the page worked. My home network is now resolving to the correct address.

[rotblitz]

"Here's the link you requested."

Yes, but that was a complete different issue, although it looked like to come with similar symptoms.  Else I would have pointed the OP at CacheCheck.  And this case was deeply discussed and investigated by me as you can see.

"It looks like the "Refresh" at the bottom of the page worked."

Ah, great to hear!  Btw, DNS propagation generally can take up to 72 hours, also independent from TTL settings.

The Sydney DC still does not respond.  It could be that there's a problem.  If you told OpenDNS your findings in your ticket, staff will certainly look after it.

[rotblitz]

This problem should have been solved in the meantime: 
https://support.umbrella.com/hc/en-us/articles/115004591763