Comments

1 comment

  • Avatar
    rotblitz (Edited )

    Too bad that you didn't show the "Diagnostic info" in your screen shot.  It could have helped.

    Do you get an e-mail if you "Report an incorrect block"?  If not, you're not using your settings, but another user's settings, because you may not have your IP address registered at https://dashboard.opendns.com/settings/

    If it is not this, the CNAME www.engadget.com is an alias for the real name silo-14-271-pub-live-production-us-east-1.amp-aws.public.aol.com with another CNAME of silo-14-pub-live.amp-aws.public.aol.com.  So ensure that you didn't block something like aol.com or the related subdomains of it with your settings. 
    https://dashboard.opendns.com/stats/all/blockeddomains 

    "It's been over a month since I added them."

    This has nothing to do with waiting.  The time to wait is 3 minutes only if you flushed your caches too.  Else you can wait forever if you don't fix it.

    Also, the entry www.engadget.com is obsolete in your list, because engadget.com already covers this and all subdomains like www.  You can safely remove it.  It just eats up your 25 entry slots.  You better add amp-aws.public.aol.com instead, but only if this is blocked by your settings.
    https://domain.opendns.com/amp-aws.public.aol.com

Please sign in to leave a comment.