Plymouth Rock / Palisades OpenDNS

Mark · April 24, 2014, 11:17:59 AM

Compatibility view is not going to fix it if you can't resolve the correct address. This is for sure a DNS problem.

Hans Manhave · April 24, 2014, 11:34:58 AM

Out of IE, change DNS on workstation to 8.8.8.8, flushdns, remove IE cache, verify ipconfig /all to confirm new DNS in use, load IE10, browse to site, make sure compat mode is used for this site.

I'm out of ammo and will sit on the bench.

Mark · April 24, 2014, 11:37:29 AM

That's basically what I suggested yesterday.

8.8.8.8 returns only the correct address.

The only thing I don't understand is why that if I use Open DNS too, that I don't have the same problem. I can get to the page even thoguh a manual lookup gives the fail address first.

Jeff Zylstra · April 24, 2014, 11:39:38 AM

Silly question, but could a router setting or anti-virus setting be interfering with DNS?

Mark · April 24, 2014, 11:48:40 AM

This may actually be a problem with palisades authoritative DNS servers, or something else they do not have setup correctly. But why it only seems to effect Open DNS I do not know.

Mark · April 24, 2014, 11:50:37 AM

Lynne,

Are you a paid Open DNS user?

Lynne Desrochers · April 24, 2014, 03:07:25 PM

Today at 2 it magically started working again. Would it be a naive guess to say they updated their certificate? Or one of the many changes just finally propagated? Thank you all for your help.

Mark · April 24, 2014, 03:40:35 PM

Yes, it is no longer serving the SERVFAIL record anymore. Just the single correct IP.

Excellent! Wonder if OpenDNS saw my ticket and fixed it, or if it was an issue with Palisade's DNS. May never know!

Hans Manhave · April 25, 2014, 10:22:10 AM

The OpenDNS folks take it as a personal challenge, I think, to see if they can fix/correct things. If you submitted a ticket, someone there probably followed up on it even if it was by contacting Palisades.

Lynne Desrochers · April 25, 2014, 10:44:05 AM

Here's part of the message we got back from OpenDNS:
I can confirm that several of our DNS resolving servers were seeing issues with the agentweb.palisades.com domain. I have flushed our DNS cache and this appears to have resolved the issue.

So there you go. Thank you again for everyone's help and input.
Lynne

Mark · April 28, 2014, 10:37:40 AM

Excellent!