OpenDNS Family Shield / Phishing OK / Porn Fails

[sjanke1]

I've entered the OpenDNS addresses (222, 220) into my Bell Home Hub 2000.  For good measure, I restarted the router and flushed the DNS cache on the PC.  Your example phishing site (internetbadguys) is successfully blocked but your example porn site (exampleadultsite) gets through, along with other porn sites. 

Here is the nslookup data:

nslookup -type=txt debug.opendns.com
Server:  mynetwork
Address:  192.168.2.1

Non-authoritative answer:
debug.opendns.com       text =        "server 5.yyz"
debug.opendns.com       text =        "flags 20 0 70 5950800000000000000"
debug.opendns.com       text =        "originid 0"
debug.opendns.com       text =        "actype 0"
debug.opendns.com       text =        "source 64.228.211.18:11943"

nslookup exampleadultsite.com
Server:  mynetwork
Address:  192.168.2.1

Non-authoritative answer:
Name:    exampleadultsite.com
Address:  67.215.92.210

So yeah, it's getting to the real IP address, but just for the porn site.  The phishing site is blocked correctly.  Any ideas on what to do?

[See update below]

[sjanke1]

OK, I switched to OpenDNS Home Free, set up the account, configured the settings on the dashboard, and it's working fine.  But I'm surprised that Family Shield, which is a lightweight solution requiring no dashboard or configuration beyond setting up the DNS values, failed.  No matter -- it's working now, and I can better control web usage in the house.

[rotblitz]

"But I'm surprised that Family Shield, which is a lightweight solution requiring no dashboard or configuration beyond setting up the DNS values, failed."

The problem was that you did not configure the OpenDNS FamilyShield resolver addresses, but the normal OpenDNS Home ones.
The FamilyShield addresses are: 208.67.222.123 and 208.67.220.123

As soon as you do it right, it works!

[sjanke1]

Ooooooh.  OK, my bad, I issed that.  It's working great now and frankly, the dashboard is rather snazzy.  Great product and I'm recommending it to friends.