1.02.2008

Looks like Earthlink has it fixed now. I wonder if they will let people know they were hacked and should scan their computers. That would be the responsible thing to do.

1 comment:

Dave B. said...

I'm still having the same problem on my earthlink nameserver 207.69.188.185:

host www.google-analytics.com 207.69.188.185
Using domain server:
Name: 207.69.188.185
Address: 207.69.188.185#53
Aliases:

www.google-analytics.com is an alias for www-google-analytics.l.google.com.
www-google-analytics.l.google.com has address 74.86.119.87

It actually now takes about 7 tries to come up with the bad ip address, usually it's the right one. I've tried reporting this to earthlink via chat and several e-mail addresses, but several hours of efforts were unable to break through their defenses (they've turned off e-mail addresses like support@earthlink.net and the chat guy was clueless and finally agreed I should e-mail abuse@abuse.earthlink.net, but I just got an automated response from that saying my e-mail would be ignored). I'm hoping someone will put in the effort to somehow get earthlink to acknowledge and fix this problem. Also I'm not a DNS expert, could the problem be in routing tables so that sometimes the earthlink nameserver isn't even reached? I've tried running several traceroute commands to my nameserver and it looks ok to me.

Overall, it is incredible that this basic a security flaw could exist for over a week and I can't even succeed in telling earthlink about it.