10-14-2019 08:11 AM
I disabled site blocking in Settings, but I'm still getting adult sites blocked. New OpenDNS user, running the Updater on both computers. How do I get free of site blocking, please?
FYI
I entered OpenDNS servers on both my computers (because I need them to both have a static IP for port forwarding). At this point I already had this site-blocking issue, but then I also entered OpenDNS servers onto my router for my wifi devices (I read on the Internet that this was OK since the computers would ignore the router's DNS).
10-15-2019 01:21 AM
It seems you forgot to clear your two local caches once after the settings change. Caches can be really persistent.
https://support.opendns.com/hc/en-us/articles/227988627
Also, ensure that your IP address is registered at https://dashboard.opendns.com/settings/
10-15-2019 09:17 AM
Thank you very much for your helpful reply, rotblitz!
You're right I didn't know I needed to attend to my Chrome browswer caches; so I did for the whole account (not just that machine which I could have done by logging out of my google account) on both machines.
Though that still hasn't fixed the issue.
I not only followed that article's advice to "Clear Browsing Data", I then also followed advice at https://www.maketecheasier.com/clear-chrome-dns-cache/ to
chrome://net-internals/#dns
chrome://net-internals/#sockets
Before and after I did
ipconfig /flushdns on both machines.
I did these all a bunch of times in different orders. Then I rebooted.
I'm not totally sure what "registered" means but I had added my IP on that Settings page:
10-15-2019 12:44 PM
"I'm not totally sure what "registered" means"
This is what I mean (from https://dashboard.opendns.com/settings/):
Copy & paste the complete plain text output of the following diagnostic commands to here. Replace example.com by the domain name of the site which should not be blocked but is.
nslookup -type=txt debug.opendns.com.
nslookup whoami.akamai.net.
nslookup example.com.
10-15-2019 01:11 PM
Thanks rotblitz, before I clicked to the screen I printscreened it looked exactly like the one you did. Here's my text output from those commands with a sample adult site:
===============================
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\>nslookup -type=txt debug.opendns.com.
Server: resolver2-fs.opendns.com
Address: 208.67.220.123
Non-authoritative answer:
debug.opendns.com text =
"server m17.pao"
debug.opendns.com text =
"flags 40020 0 8050 180000000000000000003950800780000000000"
debug.opendns.com text =
"originid 321570992"
debug.opendns.com text =
"actype 2"
debug.opendns.com text =
"bundle 12276272"
debug.opendns.com text =
"source 135.180.116.13:60522"
C:\>nslookup whoami.akamai.net.
Server: resolver2-fs.opendns.com
Address: 208.67.220.123
Name: whoami.akamai.net
Address: 2620:0:cc3::17
C:\>nslookup pornhub.com.
Server: resolver2-fs.opendns.com
Address: 208.67.220.123
Non-authoritative answer:
Name: pornhub.com
Addresses: 146.112.61.106
146.112.61.106
C:\>
10-15-2019 03:05 PM
Lol - nothing blocked! If you configure the normal resolver addresses instead of the FamilyShield ones, nothing will be blocked anymore.
10-16-2019 01:52 PM
Thank you very much for diagnosing my issue, rotblitz!
I had just gone with the fastest DNS server using DNSBenchmark (and it does make sense that would be a presumably relatively little-used FamilyShield one!).
Do I correctly understand from https://support.opendns.com/hc/en-us/community/posts/360054654872-sites-blocked-despite-Web-Content-Filtering-Nothing-blocked-?page=1
that to avoid FamilyShield I only need to avoid 208.67.222.123 and 208.67.220.123 , please?
10-16-2019 02:05 PM
Yes, these .123 addresses are the FamilyShield addresses which generally block adult content.
The normal addresses are: 208.67.222.222 208.67.220.220 208.67.222.220 208.67.220.222
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide