Topic 'Bad routing to OpenDNS?' in forum 'Sprint Mobile Broadband' - dslreports.com

Re: Bad routing to OpenDNS?

Mon, 01 Feb 2010 17:27:57 EDT

tomdlgns posted : got on the phone with sprint today....

spoke with someone higher up and this is what he told me.

sprint has released many usb cards/new firmware that have openDNS features built into the settings.

see below.

New features added in this release:
OpenDNS support can be found under Advanced -> Web Filter. This change allows the use of
the router's Advanced -> Web Filter -> OpenDNS content filtering functionality, or optionally,
your personal OpenDNS account settings if you have one.

more info can be found here

»www6.sprint.com/downloads/window···2009.pdf

Re: Bad routing to OpenDNS?

Mon, 25 Jan 2010 14:22:05 EDT

tomdlgns posted : i suppose. i am not very familiar with proxy programs, since i have never had a need to set them up.

this is the programs web site.

www.delegate.org

i am using version

dg9_9_6.exe

---code---
DeleGateD.exe -P53 SERVER=udprelay://208.67.222.222:5353 SERVER=udprelay://208.67.220.220:5353 PERMIT=*:208.67.*:.localnet ADMIN=youremail@domain.com
---code end----

in order for the above code to work, you need to rename the .exe file to delegated.exe (or change the code above to the default program name) i threw the .exe file in my c drive and copy/pasted that code into cmd prompt.

just a tip. once you install the program, DO NOT click the .exe file, dont go to the config page of the program, dont do anything other than copy past the link in cmd prompt.

it will ask you if you want to run it as a service and that is abut it

Re: Bad routing to OpenDNS?

Mon, 25 Jan 2010 13:55:36 EDT

AVD posted : a proxy....

Re: Bad routing to OpenDNS?

Mon, 25 Jan 2010 13:24:27 EDT

tomdlgns posted : yes, it looks to be that way.

however, since my last post, i have found out alot of good, useful information for sprint users.

i got some help from someone on the openDNS forums.

basically, sprint is redirecting all DNS on port 53, however, they are NOT redirecting DNS on port 5353.

there is a program available that allows you to use port 5353 on the computer that you have the sprint device on.

if you, or anyone else, wants more info on it, i am willing to share.

once you have the program, all you need to do are the following:

1. change your nic card to use 127.0.0.1 for dns server.
2. run a command in cmd prompt that configures the 3rd party program.
3. make sure the 3rd party program runs as a service on the PC automatically when it is rebooted.

once i did that, i was able to go to

»welcome.opendns.com and get the message saying i AM using their servers.

now, how quick before sprint figures this out? i hope, never.

it sounds confusing, but trust me, once it is configured properly, it runs very smooth.

Re: Bad routing to OpenDNS?

Mon, 25 Jan 2010 13:05:20 EDT

AVD posted :

said by tomdlgns:

i would like to post some depressing news.

it looks like sprint is hijacking DNS again...

i am very, very irritated.

mainly because i migrated one account from dynamic to static to test it with my sprint device and it worked. then i switched the rest of my devices to static and i was able to pass the test when visiting...welcome.opendns.com

it seems that 2-3 months later, they are hijacking their DNS again.

i noticed it when i logged into my opendns.com portal and noticed that there was NO data under the stats page. this set off a red flag in my book and i had to call Sprint. of course, their advanced tech support is anything but advanced.

i will update the thread when/if i hear anything.

you are saying the hijack is for both static and dynamic accounts?
--
standard disclaimers apply.

Re: Bad routing to OpenDNS?

Fri, 22 Jan 2010 20:01:52 EDT

tomdlgns posted : i would like to post some depressing news.

it looks like sprint is hijacking DNS again...

i am very, very irritated.

mainly because i migrated one account from dynamic to static to test it with my sprint device and it worked. then i switched the rest of my devices to static and i was able to pass the test when visiting...welcome.opendns.com

it seems that 2-3 months later, they are hijacking their DNS again.

i noticed it when i logged into my opendns.com portal and noticed that there was NO data under the stats page. this set off a red flag in my book and i had to call Sprint. of course, their advanced tech support is anything but advanced.

i will update the thread when/if i hear anything.

Re: Bad routing to OpenDNS?

Mon, 28 Dec 2009 13:42:19 EDT

tomdlgns posted :

said by AVD:

two questions:

1) My usage is grandfathered. Will I loose that if I switch to a static IP?

2) Can you connect into your network with a static IP? AFAI can tell all inbound requests are dropped.

i was grandfathered as well, i still have unlimited usage. i switched to static about 3 months ago.

i am not sure what you mean for question number 2.

Re: Bad routing to OpenDNS?

Mon, 28 Dec 2009 13:34:43 EDT

AVD posted : two questions:

1) My usage is grandfathered. Will I loose that if I switch to a static IP?

2) Can you connect into your network with a static IP? AFAI can tell all inbound requests are dropped.
--
standard disclaimers apply.

Re: Bad routing to OpenDNS?

Mon, 28 Dec 2009 10:05:43 EDT

tomdlgns posted :

said by powerspec88:

Does anyone else get this when they do a trace route to 208.67.222.222? Looks like im being routed to Amsterdam....

Tracing route to resolver1.opendns.com [208.67.222.222]over a maximum of 30 hops: 1     2 ms    <1 ms    <1 ms  192.168.1.12    68 ms    66 ms    60 ms  68.28.81.693    89 ms    63 ms    69 ms  68.28.81.924   105 ms    74 ms    68 ms  68.28.83.555     *        *        *     Request timed out.6    70 ms    62 ms    86 ms  68.28.87.97     *        *        *     Request timed out.8    74 ms    92 ms    74 ms  68.28.85.699    78 ms    82 ms    63 ms  sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.225]10    86 ms    81 ms    80 ms  sl-crs2-chi-0-15-2-0.sprintlink.net [144.232.24.206]11   104 ms   227 ms   144 ms  sl-crs2-nyc-0-8-0-1.sprintlink.net [144.232.20.119]12   103 ms   120 ms   102 ms  sl-gw35-nyc-15-0-0.sprintlink.net [144.232.13.39]13   115 ms   124 ms   111 ms  sl-tisca1-288264-0.sprintlink.net [144.223.128.182]14   190 ms   191 ms   239 ms  xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]15   216 ms   211 ms   215 ms  opendns-gw.ip4.tinet.net [77.67.66.70]16   237 ms   201 ms   194 ms  resolver1.opendns.com [208.67.222.222]

if you get a static ip address from sprint, you can use any DNS server you want.

i was having issues with DNS getting re routed to sprint even when i had the static openDNS servers, however, i was still using an automatic IP from sprint.

the only thing they added to my monthly account was $1.99 per device with a static ip address.

now that i am static, openDNS work w/o any problems.

Re: Bad routing to OpenDNS?

Wed, 21 Oct 2009 22:36:14 EDT

powerspec88 posted : I know I can't use OpenDNS, I was just wondering if anyone else is getting this. I use OpenDNS DNS servers for ping testing but not anymore.

Re: Bad routing to OpenDNS?

Wed, 21 Oct 2009 14:38:58 EDT

brianhayes posted : Sprint EVDO uses it's own DNS servers. I contacted OpenDNS since I've used it for years. OpenDNS replied that there's conflicts and I should use Sprint defaults until they work it out or until Sprint gets with the program.

Bad routing to OpenDNS?

Mon, 19 Oct 2009 06:06:21 EDT

powerspec88 posted : Does anyone else get this when they do a trace route to 208.67.222.222? Looks like im being routed to Amsterdam....

Tracing route to resolver1.opendns.com [208.67.222.222]over a maximum of 30 hops: 1     2 ms    <1 ms    <1 ms  192.168.1.12    68 ms    66 ms    60 ms  68.28.81.693    89 ms    63 ms    69 ms  68.28.81.924   105 ms    74 ms    68 ms  68.28.83.555     *        *        *     Request timed out.6    70 ms    62 ms    86 ms  68.28.87.97     *        *        *     Request timed out.8    74 ms    92 ms    74 ms  68.28.85.699    78 ms    82 ms    63 ms  sl-crs1-kc-0-15-0-0.sprintlink.net [144.223.137.225]10    86 ms    81 ms    80 ms  sl-crs2-chi-0-15-2-0.sprintlink.net [144.232.24.206]11   104 ms   227 ms   144 ms  sl-crs2-nyc-0-8-0-1.sprintlink.net [144.232.20.119]12   103 ms   120 ms   102 ms  sl-gw35-nyc-15-0-0.sprintlink.net [144.232.13.39]13   115 ms   124 ms   111 ms  sl-tisca1-288264-0.sprintlink.net [144.223.128.182]14   190 ms   191 ms   239 ms  xe-7-0-0.ams10.ip4.tinet.net [89.149.185.89]15   216 ms   211 ms   215 ms  opendns-gw.ip4.tinet.net [77.67.66.70]16   237 ms   201 ms   194 ms  resolver1.opendns.com [208.67.222.222]

--
»twitter.com/powerspec | »netisinc.com | »speedtest.kcmogaming.net
Home Internet: Sprint Mobile Broadband, DSL line: AT&T 6/768
Server: 100Mbps with Cogent/Level3, Work: 550Mbps Total with AT&T and EverestKC/Surewest