Wrong domain blocked customisation

[ValbrunaUK]

Hi All, 

I couldn't see if any one had posted this before but I noticed today that I see the wrong domain blocked customisation.  My account customisation hasn't changed in a long time and nothing on our network should be interfering.  The outside IP address is static and hasn't changed.

Would someone be able to shed some light on things.  I've used another PC in another location which is going through the same settings in OpenDNS and it's fine.

Lost and confused.

Chris

[rotblitz]

"I see the wrong domain blocked customisation."

The information provided is not sufficient.  What exactly do you see (screen shot?), and what would you expect to see instead?

[ValbrunaUK]

This is what I'm currently seeing: "blocked domain"

and what I should see: "correct domain"

correct domain.png
blocked domain.png

[ahoncian]

Hi Valbruna,

There's a possibility that you're leased a different IP address that is also configured with OpenDNS. We sent a ticket to your email with a diagnostic link so we can take a look at this issue. We are looking forward to assisting you.

Best regards,

Anthony Honciano
OpenDNS
Customer Service Representative

[rotblitz]

You would perform a "nslookup myip.opendns.com." to see what IP address OpenDNS sees from your DNS queries.  This IP address is used to associate your content filtering, security settings and stats with you.

And visiting http://myip.dnsomatic.com/ would show you the IP address OpenDNS is seeing from your browser web traffic to them.  This is used to associate your page customization with you.

That said, if the two IP addresses (DNS and web) do not match, then the one part or the other part of your settings will not work as expected.  Even more, if none of these IP addresses is registered with your network at https://dashboard.opendns.com/settings/ then none of your settings will take effect.

So proceed with what Anthony advised to get you sorted.

[ValbrunaUK]

Argh! I had a reply typed and lost the tab!! Grr

Basically, we are on a static IP address. I tried the nslookup and found it wasn't performing.  

Doing a little more searching I found the server had rebooted and something had snagged up the DNS forwarder.

I think I have it sorted now.

Sorry to be a trouble.  It has all worked for such a long time with the settings we have.  I wouldn't have thought a server reboot would have hiccup'd it so much.

Thanks again.

Chris

blocked domain 2.png

[rotblitz]

This does not really make sense.  If you had non-OpenDNS resolver addresses as forwarders, you would not see an OpenDNS block page at all, no matter if customized or not, unless they were still in your local cache.  But you did get those block pages.  That said, there must have been something else.

[ValbrunaUK]

I haven't explained it very well. Sorry.  I have both OpenDNS IP's in for DNS as well as another for a server in another branch.  The letter being the problem.  Doing an nslookup on myip.opendns.com failed with the 2 sec timeout.  Took out the last entry and everything was fine.  I think the system was doing a round robin and falling over.

I know it was very strange.  Seeing the wrong block and the right customisation and then the wrong one again.

I can confirm it is all working like it should - at the moment 🙂

[rotblitz]

"as well as another for a server in another branch"

Ah yes, this makes indeed sense.  If you mix in non-OpenDNS resolvers, you definitely do not use OpenDNS constantly and reliably, but randomly only.

"Doing an nslookup on myip.opendns.com failed with the 2 sec timeout."

This again was unrelated and just by coincidence.  OpenDNS returns your (DNS) IP address, and any other service returns NXDOMAIN, i.e. only OpenDNS is able to  resolve this name.  If you got a timeout, then this other DNS "server in another branch" has lousy response times...