gmail blocked by open dns

[cocoathedog]

I can't access my gmail now that I'm using open dns. Here is the error message:

This is probably not the site you are looking for!

You attempted to reach mail.google.com, but instead you actually reached a server identifying itself as*.opendns.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version ofmail.google.com.

You cannot proceed because the website operator has requested heightened security for this domain.

[mattwilson9090]

Adding mail.gmail.com was redundant and unecessary since it is a subdomain of gmail.com

gmail.com alone will whitelist ALL of it's subdomains, and has the benefit of only requiring 1 slots in your whitelist instead of the 2 you used.

[lands4]

I'm still studying the behavior OpenDNS but I'm finding that subdomains are blocks.  For example, I find that I am able to use most of google.com but I can see that I am blocked from subdomains and confirm in my blocked domain logs the following sites are blocked.

play.google.com
mtalk.google.com
inbox.google.com
drive.google.com

I'm going to test wildcards like *.gmail.com and *.google.com.

[lands4]

Okay, it would not accept wildcards (*).

@mattwilson9090, you were right I don't need subdomains if you have the root of the domain entered.  That seems logical but I realized my problem was that I hadn't put in google.com because it worked for searching.  

So the result is that if you want to open every *.google.com just enter the root google.com.  For people that may want to be more selective, you could just add each subdomain i.e. play.google.com, docs.google.com and so forth but keep in mind that some of these use multiple subdomains.  Examples I saw mail.google.com, mail.gmail.com, docs.google.com, drive.google.com and several more.

If you are like me and choose High Filter and then add a bunch more filters with the customize option then you will most likely need to selectively allow.  Below is my setting.  We use many google services.  I post because it may help others.

Filters:

  Academic Fraud

  Adult Themes

  Adware

  Alcohol

  Anime/Manga/Webcomic

  Auctions

  Automotive

  Blogs

  Business Services

  Chat

  Classifieds

  Dating

  Drugs

  Ecommerce/Shopping

  Educational Institutions

  File Storage

  Financial Institutions

  Forums/Message boards

  Gambling

  Games

  German Youth Protection

  Government

  Hate/Discrimination

  Health and Fitness

  Humor

  Instant Messaging

  Jobs/Employment

  Lingerie/Bikini

  Movies

  Music

  News/Media

  Non-Profits

  Nudity

  P2P/File sharing

  Parked Domains

  Photo Sharing

  Podcasts

  Politics

  Pornography

  Portals

  Proxy/Anonymizer

  Radio

  Religious

  Research/Reference

  Search Engines

  Sexuality

  Social Networking

  Software/Technology

  Sports

  Tasteless

  Television

  Tobacco

  Travel

  Video Sharing

  Visual Search Engines

  Weapons

  Web Spam

  Webmail

ALWAYS BLOCK:
tumblr.com

NEVER BLOCK:
cardgames.io
comcast.net
dropbox.com
edmodo.com
facebook.com
gmail.com
google.com
icloud.com
linkedin.com
live.com
nextdoor.com
office.com
skype.com
pinterest.com

[rotblitz]

"I'm still studying the behavior OpenDNS but I'm finding that subdomains are blocks."

Yes, subdomains may be categorized differently in the domain tagging system.   All normal.

"I'm going to test wildcards like *.gmail.com and *.google.com."

You cannot, because gmail.com already means gmail.com and *.gmail.com.  And google.com means already google.com and *.google.com.  This is very well documented in the knowledge base.  Nothing to be surprised about.

[lrsmetak]

I had tried everything on this forum to get my gmail to work (with all the domain white-listing) and eventually discovered that I just had to uncheck "Webmail" as a blocked category. I had misunderstood what that category was for. As soon as I unchecked it, my Gmail was completely back to normal (with gmail.com and accounts.google.com white-listed)

[serendipitologist]

I came here because gmail was being blocked. I eventually discovered that there was truth to the response that rotblitz gives however there is truth to what others say regarding certificates. the responses that are given regarding that aspect of the discussion are less than helpful and leave me feeling that openDNS must be a sloppy organization. from a purely diagnostic view point it is necessary to receive clear feedback as to what is happening. to blame a web browser for doing it's job as an explanation for bad feedback seems sloppy. perhaps a differant flag would be tripped past the first one but the the first error message is in fact due to an unrecognized  encryption certificate issuer. on firefox at least, this is the error message.

    Someone could be trying to impersonate the site and you should not continue.

    Websites prove their identity via certificates. Firefox does not trust mail.google.com because its certificate issuer is              unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.

    Error code: SEC_ERROR_UNKNOWN_ISSUER

my point is that diagnostic would easier if openDNS could find a way for an actual page to be reached to tell the user it was indeed blocked by openDNS. to not only not do this but also completely disregard any mention of what could be done to do it is what feels sloppy. I had to read completely through everything to feel confident that the problem was in fact that it was blocked and that there wasn't a different problem somewhere. this is after I had to do significant research to determine that openDNS might be the reason for the problem. please try to find a way to get a message to a user telling them that you blocked the site so it doesn't feel like something is broken somewhere when it isn't. thank you.

[rotblitz]

I recommend reading this.
https://support.opendns.com/hc/en-us/articles/227987007-Block-Page-Errors-Installing-the-Cisco-Umbrella-Root-CA
You cannot expect that a seven year old thread is current.

[serendipitologist]

and now the thread is up to date :)

[rotblitz]

Not really. This thread is about Gmail being blocked. We became a little bit off-topic. ;-)