Reply #79: Yes, if you have tried to set custom dns address on your wifi adapter

[kenny blankenship]

but nslookup (run w/ no options) doesn't report that address, then some option -or action- of that device/adapter is ignoring or interfering with what you told it about DNS.

Now that I know the type of internet connection you have and the device name, I have found this from opendns.org's support forums:
http://forums.opendns.com/comments.php?DiscussionID=6185

#
Can't point get OpenDNS working with Sierra Overdrive 3G/4G Mobile Hotspot

Still getting message: "Oops. You're not using OpenDNS yet."

Have changed my DNS settings as follows:

Overdrive Advanced Settings>Router>LAN>DNS Mode=Manual>Manual DNS Servers = 208.67.222.222, 208.67.220.220
Have tried both DNS Relay=Enabled AND DNS Relay=Disabled

Still no luck. Any suggestions? Thanks.


User Guide for device:
http://support.sprint.com/global/pdf/user_guides/sierra_wireless/overdrive_3g4g/overdrive_3g4g_sierra_wireless_ug.pdf
#

* CommentAuthordiacon
* CommentTimeFeb 12th 2010

permalink
Sprint's network doesn't allow for using other DNS servers. There is a work around though that would have to happen on each machine.

Here's the latest thread with info about Sprint and this issue:

http://forums.opendns.com/comments.php?DiscussionID=6021&page=1#Item_42

It isn't just that the Overdrive hotspot is overriding your settings, Sprint is redirecting your outbound traffic over port 53 (used for dns) and not letting it connect to opendns or google or anybody else! They do this on their own routers, and it's completely beyond your ability to control. Sorry for all the posts that tell you "just do this, and your problem will be solved" or "make sure you didn't screw up this other thing." In this case, no friendly advice or assurances that "it's not that hard!" can work because you're up against your own ISP's sabotaging of an internet protocol. My ISP, like just about every other ISP these days, will not allow any host to contact my machine over tcp port 25. It's an antispam thing, but it breaks your ability to have your own mail server without elaborate countermeasures.

There may be a workaround using a program called Delegate ( www.delegate.org )that you can use to cause your own dns lookups to go out over a different port (5353, for example) instead of over the normal port 53. Delegate appears to be a multipurpose, swiss-army-knife style port redirector, so expect lots of configuration hoohaw. I have no experience with it, can't say whether it would be effective against Sprint's clear desire to capture your DNS queries, and I'm pretty sure it would be intimidating to deal with.