OpenDNS Still blocking sites even after enabling "None - Nothing Block"

[x20a]

Hello

I'm having issues using openDNS. I just want to use their DNS as it gives me good results than Google's. I already tick "None - Nothing blocked." under filtering level so it won't blocked any site but openDNS keeps blocking it. In other words, content filtering is not working good for me. There's too much site to add one by one so enabling "None - Nothing blocked" under filtering level is a good option for me.

Any idea?

[rotblitz]

It seems you don't keep your IP address information updated at https://dashboard.opendns.com/settings/ - if your IP address changes, your DNS queries are no longer associated with your settings.  You may be using another OpenDNS user's settings then, not yours.
Go to there and update your IP address information.  Run an Updater going further which updates fully automatically.

[maxhrt]

IP updater claims it is all OK, but default blocking is still in place?

Maybe Dashboard or updater should warn that we use family shield address?

[rotblitz]

I do not see any relationship to what has been discussed here but want to comment as follows:

The Updater has nothing to do with the blocking, and default blocking (which is "none") is in place if your IP address information is not kept updated at https://dashboard.opendns.com/settings/ for whatever reason.

Why should something warn about what you have willingly configured yourself?  This does not make sense, and most users would be annoyed by such warnings.

[maxhrt]

"Why should something warn about what you have willingly configured yourself?  This does not make sense, and most users would be annoyed by such warnings."

It makes sense when user decides to use Home service, but user may not realize that Home service need another default servers. Updater tool may find needed info from ipconfig /all

[rotblitz]

"Updater tool may find needed info from ipconfig /all"

You too...
And no, most ipconfig /all do not show external resolver addresses, but ideally the router's IP address, because properly working routers act as DNS servers and forwarders.  External DNS resolvers on the DHCP/LAN side is suboptimal and just a workaround for routers where one cannot configure the WAN side.

In an ideal case you cannot figure out with locally operating commands what external DNS server addresses are being used.

And again, I still do not see a relationship to what has been discussed in this thread.  Or do you mean that x20a could have configured the FamilyShield addresses, thus blocking even if the dashboard content filtering level is "none"?  This could well be...

[maxhrt]

Yes, IP updater should react in rare case when FamilyShield address is configured at OS level. Updater tool can also mislead user when displaying that it is using OpenDNS and user will think it is all right. At least it should say that this tool is not needed for FamilyShield?

To use FamilyShield, you should set your DNS server entries: 208.67.222.123 and 208.67.220.123.  On our website, you'll may notice that OpenDNS' DNS servers are 208.67.222.222 and 208.67.220.220, but these do not apply to FamilyShield customers.