US ISPs Continue To Support DNSChanger Redirection Servers
darthcamaro writes "On Monday of this week, the primary servers that kept those infected with the DNSChanger malware were taken offline. It's a story that sparked lots of media hype with people claiming that hundreds of thousands of people could lose their Internet access. As it turns out, major U.S. ISPs including Verizon, Cox, AT&T and CenturyLink all kept their own DNSChanger servers online, protecting any users from losing their access."
Don't all of those ISPs play that dirty trick of redirecting failed DNS lookups to advertising? Why don't they just set their DNSchanger servers to redirect all lookups to some page telling the user that their system is infected and how to download a tool to fix it?
Sure it will break everything but http(s) but if they are happy to do it for money why aren't they happy to do it for the common good?
When information is power, privacy is freedom.
Knock them off the internet already so they know they have a problem. DNSChanger is probably not the only issue they have.
"I use a Mac because I'm just better than you are."
Next article please
On a side note, can anyone tell me why all of the ads I see are for AT&T?
That's why I didn't get a phone call from my parents asking me to fix their Internet.
This is a fail. The problem will not go away if we keep coddling people that have infected machines.
Hundreds of thousands of people are going to launch their internet like an arrow?
Neat!
That was the problem initially, the computers were too loose and malware got in.
typo in text loose should be lose
I don't know the meaning of the word 'don't' - J
"...protecting any users from losing their access."
This had nothing to do with protecting users. This was because the ISPs didn't want to be overwhelmed with support calls and have to deal with X ignorant and pissed off customers who don't know DNSChanger from a hot dog and who will just blame the ISP for any outage.
blindly antisocialist = antisocial
What will it take for people to start taking security seriously? One of these days a major botnet will wipe a few million hard drives with no warning. I'm not convinced that even that would do it.
Bravo! That's what they call "network neutrality"!
We have AT&T (bellsouth.net) and yesterday internet access was spotty at best. Some sites loaded right away as usual, some never loaded, some now and then. Ebay was a lost cause, google was ify and google hits went nowwhere. At work we have comcast and it was business as usual.
At home it made no difference which computer I used, MAC, PC, Linux all had issues. My router / DSL modem is a Motorola.
It's cheaper to keep it broken than to get customers to go fix it. Duh.
Mod me down, I shall become more off-topic than you could possibly imagine.
Make ISPs responsible (and if they want they can make their customers responsible). Now they can have tens if not hundreds of zombies within their network, knowingly and doing nothing since they might lose customers. Not going to happen; $$$$.
Perl Programmer for hire
Somebody should tighten that sucker up for 'em.
Just shows that the Internet can take care of itself, and government meddling is not needed.
this will be bad news though, we should be trying to force the ISP to keep their hands OFF our data.
The ISPs did not have dedicated servers for DNSChanger, they have been filtering your DNS traffic all along.
You are being MICROattacked, from various angles, in a SOFT manner.
Pretty altruistic of them!
What?! Keeping people in the dark about compromised computers so they don't have to pay for tech support is altruistic in your view?!
Now I have to put up with another round of fielding questions when the media gets another Scary Computer Story Boner when they turn *these* severs off?
I'm also waiting for the malware that gets installed via scareware over this whole bullshit.
DNSSEC-enabled stub resolvers on the client and/or browsers would have stopped this from ever becoming a problem. Of course, the bad guys would have just disabled this feature and/or replaced the root key on the clients, if they had access. However, it sounds like much of the time it was a vulnerable router that had the dns settings changed. In this case, the clients would have detected false/forged DNS records and stopped the problems sooner..