OpenDNS blocking text message images

[optionalnecessity]

Just installed OpenDNS yesterday.  Have Comcast cable service.  modem is motorola surfboard, router is linksys E2000.

Domain blocking is behaving as expected, but I have one unexpected side effect...  I can no longer receive MOST images within text messages.  I say MOST because I am becoming someone convinced it could be a file size limitation...  could that be it?

All Images within text messages work again if:

wifi is disabled on my phone.

wifi router is turned off.

openDNS is disabled.

Any thoughts?

[mattwilson9090]

OpenDNS, or any DNS system knows nothing about file sizes. It only knows about domain names.

I have no idea what software you are using for these text messages, or even whether they are truly SMS messages or something else entirely, but the only way that OpenDNS would be preventing you from receiving images is if those images are coming from a domain that your own OpenDNS settings are blocking.

You'll need to look at the images themselves, or the links to them, as well as your OpenDNS settings and OpenDNS stats and logs to see where the issue lies.

[wheberling3]

The above discussion appear to come closest to what I am experiencing.

I use AT&T Cell phone service with a dataplan. When on WIFI at home, I found that SMS pass correctly but MMS do not. I set OPENDNS to block nothing and no change occurred. However when I allowed my home router to revert to using Verizon's DNS, MMS passed through unhindered. So OPENDNS appears to be blind to the specific domain required to send/receive MMS on AT&T's network.

Any suggestions?

[rotblitz]

You check at https://dashboard.opendns.com/stats/all/blockeddomains to see if there are any blocked domains nevertheless.  If not, your issue is not related to OpenDNS.

[wheberling3]

My phone lists http://mmsc.mobile.att.net & proxy.mobile.att.net in the setup. When viewing the domains I found that att.net has many flavors, some of which are marketing etc. which are not appreciated Thus some are blocked. Rather than comb through which custom setting is doing the blocking I just set att.net to never be blocked on my account. That worked.