Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
The Internet Networking The Almighty Buck

RoadRunner Intercepting Domain Typos 337

shaunco writes "Sometime around midnight on February 26th (at least for the SoCal users), TimeWarner's RoadRunner service started intercepting failed DNS requests, redirecting them to RoadRunner's own search and advertising platform. To see if this has been enabled in your area, try visiting {some random string}.com in your Web browser. This feature subverts user preferences set within browsers, which allow the user to select which search engine receives their typos and invalid domains. RoadRunner users can disable this function — or they can just use OpenDNS. Here is an example RoadRunner results page.
This discussion has been archived. No new comments can be posted.

RoadRunner Intercepting Domain Typos

Comments Filter:
  • by themushroom ( 197365 ) on Tuesday February 26, 2008 @02:34PM (#22561472) Homepage
    Roadrunner's not-found page seems roughly as useful as the default MSN Search page that IE puts up automatically if a page can't be found. Which is to say, not very.

    But it's still nowhere near as worthwhile as the "what you want, when you want it" domain squatter pages where most of the links are porn and ads. Catch up, Roadrunner!!

  • ATT does it as well (Score:2, Interesting)

    by B00yah ( 213676 ) on Tuesday February 26, 2008 @02:34PM (#22561480) Homepage
    They've been doing it for about a year. i always thought it was fairly shady, but they rationalized it by saying other ISPs were doing it as well.
  • by Ars Dilbert ( 852117 ) on Tuesday February 26, 2008 @02:44PM (#22561642) Homepage
    My DNS server queries root servers directly, so any poisoning by an ISP would not affect my home network.

    The Site Finder stunt NetSol/Verisign pulled a few years ago, that was done on the root servers, wasn't it? That was a lot more disruptive than an ISP creating a catch-all DNS zone on their little DNS boxes.
  • Re:OpenDNS Guide (Score:1, Interesting)

    by idontgno ( 624372 ) on Tuesday February 26, 2008 @02:47PM (#22561694) Journal

    And what's your upstream DNS provider? If it's Road Runner, I bet you'll get bogus A records returned, no matter what protocol you intend to use the resulting IP address with. Similarly with OpenDNS, as far as I can tell.

    And I hope for your sake you're running a recent version of BIND. That thing is epic in terms of ancient (but now closed) remote exploit opportunities.

  • by ivanmarsh ( 634711 ) on Tuesday February 26, 2008 @02:56PM (#22561832)
    My Charter service does the same thing. Leave it to a bunch of marketing nimrods to disable a troubleshooting tool so you can't tell the difference between a page not found, site not found or DNS error.

    So... I simply blacklisted Charter's redirection site in my firewall and proxy server.
  • by Anti-Trend ( 857000 ) on Tuesday February 26, 2008 @03:07PM (#22562022) Homepage Journal
    OpenDNS is actually substantially worse. At least Roadrunner is obvious about the fact that you're visiting their servers. With OpenDNS, it seemed they were actually proxying requests for well-known search engines that were *not* typo'd in order to grab stats. Try setting your DNS resolvers to OpenDNS, then dig (or 'nslookup' for you Windows folks) www.google.com. Do a whois on the resulting IPs, and guess who they're registered to... Google? Nope, OpenDNS! At least, last I checked -- that was also the last time I used OpenDNS.
  • Re:OpenDNS Guide (Score:1, Interesting)

    by Anonymous Coward on Tuesday February 26, 2008 @03:38PM (#22562618)
    And hope that the provider's DNS servers are not acting as transparent proxies for the root servers....
  • by Anonymous Coward on Tuesday February 26, 2008 @03:39PM (#22562628)
    You're not doing it right.

    > dig www.google.com @resolver1.opendns.com

    [...]
    ;; ANSWER SECTION:
    www.google.com. 30 IN CNAME google.navigation.opendns.com.
    google.navigation.opendns.com. 30 IN A 208.69.34.230
    google.navigation.opendns.com. 30 IN A 208.69.34.231
    [...]

    That's right, OpenDNS not only does the same kind of typo-redirection through DNS as RoadRunner, they also intercept www.google.com URLs. Instead of advertising such a shady service, geeks should show people how to run their own resolvers. It isn't hard at all.
  • Re:OpenDNS Guide (Score:5, Interesting)

    by MadAhab ( 40080 ) <slasher@nospam.ahab.com> on Tuesday February 26, 2008 @03:48PM (#22562796) Homepage Journal
    I just programmed my cable modem to use 4.2.2.1-3 for DNS. Problem solved. At work, under a RoadRunner business connection, we've long run our own DNS because the RoadRunner DNS servers have always been just shit.

    Suspiciously, however, I didn't turn off the "service". Someone at the other end did it. I refused to give them my phone number, so either they used caller ID to pull up my account without my consent, or they blacked out my cable modem MAC when I started portscanning the server and looking up a hundred variations of www.stopfuckingwithmydnsroadrunnersucksdogballs.com.

    All around evil. Cable companies are doing this to boil the Net Neutrality frog, have no doubt about it.
  • by raju1kabir ( 251972 ) on Tuesday February 26, 2008 @04:22PM (#22563330) Homepage

    www.google.com. 30 IN CNAME google.navigation.opendns.com.

    Thanks for the heads up. I've just removed OpenDNS from my router's configuration. My ISP's DNS sucks but there are some caching servers at work I can piggyback on.

    I wonder if this OpenDNS business explains the error page I've been getting with increasing frequency from Google, something to the effect of my query looking like it came from malware on my computer.

I've noticed several design suggestions in your code.

Working...