Comments on: Vulnerable to a DNS cache poisoning at home?

Tools and patches are available to see whether your home Internet connection is vulnerable to Dan Kaminsky's DNS flaw.
• DNS exploit code is in the wild

[BrianSeattle]

Robert, can you or someone at CNET call Comcast and crack the whip on them? I called regular support as well as their dedicated security line, and no one there had any idea what I was talking about when I asked about their status on patching their DNS servers.

I can understand if they want to be coy about exactly how far they are in the patching process - perhaps there are still a few unpatched machines - but to feign total ignorance of the issue is absurd, and a little unnerving to me as a customer.

You can find Comcast Security phone number, 888-565-4329, at security.comcast.net > Get Help > Contact Comcast Security.

If they are actually oblivious, it's downright scary. If they are just stonewalling, they need to learn that this is a very bad customer experience when the exploit has been made public.

[The_Decider]

It is easy enough to fix this on your own: www.opendns.com

[ofrmgfo]

As of 25 July 08 my comcast servers are up to date

[HeartofHistory]

Brian - if you follow the Dan Kaminsky link above, the text at the bottom of the DNS test box says, "Note: Comcast users should not worry." No reason is given, but the note is there.

[Schratboy]

More BS and bluster regarding the over-hyped vulnerability problem. For CRYING OUT LOUD PEOPLE! There are hundreds of other issues that will take your operations to its knees before even ONE (1) known vulnerability raises its ugly head. The falasy of vulnerability risk is over-sold. Not that these can't do harm, but there are plethora of threats and misuse issues than will impact operations to a greater extent NOW than waiting for an exploit to trigger a flaw.

[The_Decider]

Within a day of ICANN's gTLD announcement, ZDNet reports that a Turkish hacking group has hijacked domain names belonging to IANA and ICANN. Interestingly, only thier "alternative" names were hijacked. For example, ICANN.COM and ICANN.NET were, but ICANN.ORG was not. Similarly, IANA.COM was, but IANA.ORG was not. The same group is apparently responsible for other recent high profile domain hijinks as well.

One thing all of the hijacked names have in common is their registrar, Register.com, which was apparently able to fix the problem within about 20 minutes. Let's hope the parties involved are up-front enough to explain what happened.

https://www.dns-oarc.net/

[cohaver]

Windows New Desktop Search and Driver update service Faces the Same Problems