208.67.222.222 and 208.67.220.220 blocking content like Family Shield nameservers

[lansharked]

I'm getting this message from OpenDNS:

--------------------------------------------------------------------------
"...This domain is blocked due to content filtering.

www.exampleadultsite.com

If you think this shouldn't be blocked, please contact your network administrator.

This site was categorized in: Nudity, Pornography
Diagnostic Info
IP Address:     75.68.86.xxx
Server:     nyc16  ..."
--------------------------------------------------------------------------

My router DNS is set to the Default OpenDNS nameservers :

    208.67.222.222
    208.67.220.220
    and
    208.67.222.220

I am NOT using the Open DNS Family Shield nameservers, which are:

    208.67.222.123
    208.67.220.123

Was the default, non-Family Shield service reconfigured to behave like the Family Shield service, without telling anyone?

[rotblitz]

No, the standard resolvers should not have been reconfigured, and only phishing and some malware domains should be blocked by default.

The following possibilities for the symptom come to mind:

• You tried out adult content filtering before, but didn't flush both your caches after the settings change, local resolver cache and browser cache.
  Flush your caches: https://support.opendns.com/entries/26336865
• Your DNS IP address is not registered with your dashboard network, but with someone else's or a secondary network of yours.  (This can happen!)
  Take corrective action: https://dashboard.opendns.com/settings/ and flush your caches.
• You have at least one of Nudity or Pornography categories selected for blocking.
  Uncheck the categories, and flush your caches.
• Although you have configured the standard OpenDNS resolvers on the router, one or two FamilyShield addresses may be configured on the computer.
  Reconfigure the computer's IPv4 connection to obtain the settings automatically via DHCP, and flush your caches.

[lansharked]

Looks like my dynamic IP address from Comcast had been registered by a different OpenDNS account. I submitted an OpenDNS helpdesk ticket to release the address from that user, but the quickest solution turned out to be to force Comcast to give me a new WAN IP by cloning my router's MAC address to a slightly different address (changed the last digit of the MAC address), and rebooting the modem and router.

[rotblitz]

Excellent!

[mattwilson9090]

@lansharked If you haven't already done so make sure that you are running an updater to keep your address registered to your OpenDNS account otherwise it's possible that this issue could repeat itself when your address changes again in the future.