Plymouth Rock / Palisades OpenDNS

[Lynne Desrochers]

I have a carrier Plymouth Rock that I can't get into their website. I keep getting an OpenDNS error. On IE i first get a certificate error, then get the opendns error. We have put in exceptions and still can't get past it. When you try it on Chrome you just get the message that the web portal does not work on chrome.
Where I'm trying to get to is: agentweb.palisades.com
This isn't the first time I've been stymied by OpenDNS. Should I just move on from it at this point? Is anyone able to get to the above website that does have OpenDNS?
Thank you.

[Mark]

Works for me with OpenDNS, and IE10 using compatibility mode.

Visited agentweb.palisades.com and got a login screen (after selecting compatibility mode and reloading the page.

[Lynne Desrochers]

Hmmm. IE 10 here as well, but still no luck with our without Compatibility view.

[Mark]

This is interesting.  I am able to load the website, but a nslookup comes back with OpenDNS server fail.  It returns an OpenDNS IP address and a second address.  Actually, I've gotten two different 205 IP Addresses.  Something is definitely up with OpenDNS and I'll get to that in a second.

Try putting this into your browser:  https://205.153.90.180

[Mark]

Their cache is correct.  I did open a ticket for the heck of it since I am logged in, but I do not understand why I can load the page and you can't. 

EDIT: Maybe it is how you have your forwarders setup.  Mine are as follows:

• 208.67.222.222 <-- OpenDNS
• 208.67.220.220 <-- OpenDNS
• 8.8.8.8 <-- Google  (actually, I'm not using Google. I'm using a different one but I just read that I am not supposed to be using it )

Maybe that will make a difference.

[Lynne Desrochers]

Nope, still not working on the https://205.153.90.180.

[Mark]

Also:

Code Select Expand

ipconfig /flushdns

on that workstation.

[Lynne Desrochers]

Sorry, this is being stubborn, but no go.   

Also:

Code Select Expand

ipconfig /flushdns

on that workstation.

[Mark]

1. Try changing your forwarders on your DNS Server.
2. after changing them (try 8.8.8.8 and remove opendns for troubleshooting) flushdns
3. close Browser, dump temp files & history
4. try again

[Hans Manhave]

Message I received using OpenDNS and SeaMonkey browser:

We're sorry. You are using a browser that is not compatible with Agent Web.

The Agent Web application is designed for Microsoft Internet Explorer versions 6 through 9.

If you have Microsoft Internet Explorer 10 currently installed, follow these instructions to continue to logon to Agent Web:

    In your browser URL window, note a GREY "Compatibility View" icon just to the left of the Refresh icon. The icon looks like a piece of paper with a crack in the center.
    Click on this "Compatibility View" icon to enable compatibility mode for Agent Web. The icon will turn BLUE and the Agent Web logon screen will be presented.

If you are using another browser, such as Firefox or Chrome, Internet Explorer 9 can be downloaded here.

If you need assistance, please call e-Tech Support at 908-219-5373.


Same message using Comodo IceDragon... 

[Mark]

I think the problem is that with IE, she doesn't even get that page.  she gets the Open DNS search page that you get when a domain does not resolve.

[Hans Manhave]

Log into OpenDNS, go to Support, use Trouble shooting features?

The cache shows the same all over the world on my location.  Refresh the OpenDNS cache at the bottom of the listing of cache on OpenDNS?

IE8 works, not that it helps Lynne any.

[Mark]

Yeah, tha'ts what I found yesterday.  But doing a dns lookup on my own, I get two IP addresses returned: one is the serv fail address for Open DNS -- which is was sends yo uto the Open DNS search page when a lookup fails.

The 2nd IP address returned is in fact the correct IP address for the site.

Using any NON-OpenDNS server I get only the valid response.

[Hans Manhave]

On IE 10, goto Tools, Compatibility View Settings, add 'agentweb.palisades.com' and it works.  For me anyway.  Not until I did that.  Easiest is to go there, fail, and then use tools/compat to add it.

[Lynne Desrochers]

Done and added, even changed it to display all websites in Compatibility View. No go.

[Mark]

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]

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]

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]

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

[Mark]

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]

Lynne,

Are you a paid Open DNS user?

[Lynne Desrochers]

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]

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]

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]

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]

Excellent!