All your DNS
are belong to us.
It can't be that bad, can it?
Tweed with the patches on the elbows, thanks.
More than two weeks after security researchers warned of a critical defect in the net's address lookup system, some of the world's biggest internet service providers - including AT&T, Time Warner and Bell Canada - have yet to install a patch inoculating their subscribers against attacks, according to an informal survey of …
are belong to us.
It can't be that bad, can it?
Tweed with the patches on the elbows, thanks.
At least one of Telstra's name servers are vulnerable.
I wonder if Virgin Media would mind me injecting my own subdomain onto their DNS to replace the boring ubr.locale.blueyonder.co.uk format? :)
According to the site, AT&T Wireless is susceptible when using the isp.cingular APN. Not sure about the wap.cingular APN, but I would venture to guess the condition is the same. DNS server assigned is 22.214.171.124.
Paris, possibly susceptible, but the firewall or nat router may be interfering with her port selection policy.
Shaw Cable in Canada seems OK:
Your name server, at 126.96.36.199, appears to be safe, but make sure the ports listed below aren't following an obvious pattern.Requests seen for b14aed6a1cd3.toorrr.com:
Over here in SK, my ISP is wide open.
I am on holydays in France and connected to Orange and it seems safe ...
Your name server, at 188.8.131.52, appears vulnerable to DNS Cache Poisoning.
I sent this by email to PCCW execs weeks ago, but no response, and no change.
DNS needs to be "patched" here too
but I can bet NTT is on to it...
I know Tiscali has been something of a target for bad press before but their servers are all good according to the Check My DNS widget.
The fact that some organisations take a month to roll out an urgent security patch isn't an excuse. It's just another problem that those organisations needs to sort out.
Taking time to test thoroughly is good, but there needs to be a sliding scale of risk due to not testing and risk due to not patching.
I checked my Virginmedia DNS last night and it reported okay.
I tested the one at work this morning and its not patched (but I'm not surprised at that result).
Okay... mine's the one with the CV's in the pockets....
You list OPAL as bein unpatched but AOL & TalkTalk were patched a while back and pass the "Check Your DNS" test.
Silo - Good luck to you mate, knowing KORNET, the DNS might be patched some time in the next 10 years (along with the rest of the korean infrastructure).
A big well done to Zen for getting theirs done so quickly. I ran the test the first time it was announced and it came up with the "safe" notice.
Another reason to be happy wtih moving from BT in my own personal "phorm" protest :)
Top marks to my ISP, Eclipse. The test shows they pass :)
Stop reading the reg and get back to your holidays, Geek!
It's high time users should learn to verify SSL certificates of sites of any importance to them. This also nullifies most dangerous effects of DNS poisoning - which is not a new attack type, BTW.
IIRC they snat you away to their own servers anyway, we need dns over ssl...
Err - wot the title says
Did wonders for me, updated the linux servers bind daemon and it killed everything i really enjoyed manually rebuilding what the patch had done...
6 months to bring out this patch jeez...... fair played to the guy who found it though and kept it hush hush instead of taking advantage of the problem.
Your name server, at 184.108.40.206, appears vulnerable to DNS Cache Poisoning.
220.127.116.11 used by 3 is vulnerable... and if you are using their wireless broadband modem you cant hardcode DNS server addresses
small ISP... got WiMax air interface... works tops... but urgh! not when their DNS's are vulnerable... 18.104.22.168 and 22.214.171.124... sent their admins an email this morning...
Qu: large ISP or small ISP more responsive to something like this?
Your name server, at 126.96.36.199, appears to be safe, but make sure the ports listed below aren't following an obvious pattern.
Requests seen for 0fdf9cf5fbac.toorrr.com:
Your name server, at 188.8.131.52, appears vulnerable to DNS Cache Poisoning.
g0-1-41.ac3-u1-sal-uk.as15444.net -> netdnscache01.eng.net
Firstly, Virgin started patching for this bug a *month* before the public announcement. We're really friendly with our DNS supplier :-)
Secondly, OpenDNS works fine on Virgin Media, we don't "snat you away" (whatever that means) in any way. I suggest you update your memory with a fact or two :-)
I can confirm that VM and Pipex seem ok.
Have Bethere patched this yet?
UK Online's DNS servers are vulnerable. They're owned by Sky but I don't know if they use the same servers as Skybroadband.
Be are in the clear (unsurprising, since they are the same as O2).
Karoo's 'opt-out' DNS servers check out OK. Not sure about the default one's though.
Griffin Internet's recursive DNS servers are patched. Testing passes.
As any Be customer knows, their DNS is crap and you should be using OpenDNS anway :o)
In case you have not seen it, here is AT&T's official statement on this vulnerability:
"AT&T Response: US-CERT DNS Security Alert- announced July 8, 2008
On July 8, 2008, US-CERT issued a Technical Cyber Security Alert TA08-190B with the title 'Multiple DNS implementations vulnerable to cache poisoning.' This alert describes how deficiencies in the DNS protocol and common DNS implementations facilitate DNS Cache poisoning attacks. This vulnerability only affects caching DNS servers, not authoritative DNS servers. This alert instructed administrators to contact their vendors for patches.
The DNS community has been aware of this vulnerability for some time. CERT technical bulletin http://www.kb.cert.org/vuls/id/252735 issued in July, 2007, identified this vulnerability but at the time no patches were available from vendors.
AT&T does not disclose the name of its DNS vendors as a security measure but has implemented a preliminary patch that was available in January, 2008. The latest patch for alert TA08-190B is currently being tested and will be deployed in the network as soon as its quality has been assured.
AT&T employs best practices in the management of its DNS infrastructure. For example, the majority of AT&T's caching DNS infrastructures have load balancers. Load balancers decrease the risk significantly because hackers are unable to target specific DNS servers. As with all patches to software affecting AT&T's production networks and infrastructure, AT&T first tests the patches in the lab to ensure they work as expected and then certifies them before deploying them into our production infrastructure.
Security is of paramount importance to AT&T. AT&T has a comprehensive approach to the security of its networks and supporting infrastructures. AT&T is meeting or exceeding our world-class DNS network performance measures. We will continue to monitor the situation and will deploy software upgrades, as warranted, following our structured testing and certification process."
End of quote.
1) They claim this is the same problem reported a year ago and for which they have already patched.
2) They claim load balancers will protect against this bug. All evidence to the contrary, they have not changed their statement.
3) They claim they do not disclose the vendor of their DNS, but also claim this is a bug in BIND which they have also patched.
4) They do not acknowledge that this is an issue with the DNS protocol, rather they act as if it is a bug in a software application.
Verizon patched everything on July 10th. What is taking AT&T so long?
I'm on comcast, and I just failed the test. A little disconcerting considering they state at their test site "Note: Comcast users should not worry.". What amazes me is that these companies dont get it and carry on just as they did before....
UKOnline/Easynet seem to have patched their DNS servers within the past few hours.. so all is okay here now!
We have BT here (albeit a business line), and 184.108.40.206 comes up clean (haven't tried our secondary which is 220.127.116.11).
Your name server, at 18.104.22.168, may be safe, but the NAT/Firewall in front of it appears to be interfering with its port selection policy. The difference between largest port and smallest port was only 36.
Please talk to your firewall or gateway vendor -- all are working on patches, mitigations, and workarounds.
Requests seen for 87bba0bc964e.toorrr.com:
Other repeat runs of the test give a port range no larger than 70, and as few as 23. Doesn't this make it easier for the bad guy to win the race, or is it the router I am sitting behind that is doing this?
Running the test on my Verizon connection got me the "appears to be safe" message, along with the "make sure the ports ..." bit.
I didn't get the port range message you got, so it might well be your router settings.
Your name server, at 22.214.171.124, appears to be safe, but make sure the ports listed below aren't following an obvious pattern.
Requests seen for 4f5029e03184.toorrr.com:
Note: dnsnode1-x4.stlsmo.sbcglobal.net [126.96.36.199]
Appears to be sorted
Your name server, at 188.8.131.52, appears to be safe,
Requests seen for f3050306b5b3.toorrr.com:
Your list may not be that accurate AOL runs on the Carphone Warehouse servers and appears not to be suseptible to this attack.
Boffin for obvious reasons
"Demon Internet was reported as potentially being vulnerable"
No. It produces similar messages to that produced by Verizon e.g
'Your name server, at 184.108.40.206, may be safe, but the NAT/Firewall in front of it appears to be interfering with its port selection policy. The difference between largest port and smallest port was only 247.
Please talk to your firewall or gateway vendor -- all are working on patches, mitigations, and workarounds.'
Your name server, at 220.127.116.11, appears to be safe, but make sure the ports listed below aren't following an obvious pattern.
Requests seen for 9184eaf37373.toorrr.com:
As I said in earlier post this is Carphone whorehouse server
18.104.22.168 (alpinetdns.mycingular.net) appears to have GREAT source port randomness and GREAT transaction ID randomness.
But it still fail's Kaminsky's (Doxpara) test.
Paris, a great source of port randomness.
Somewhat to my surprise. Somebody at Telus is paying attention.
The thing I find interesting is that some very large ISPs seem to have no mechanism in place for fast tracking critical changes. Sometimes a patch is so important and so urgent that if it makes the system fall over, that's still a better situation than running without the patch.
Your name server, at 22.214.171.124, appears vulnerable to DNS Cache Poisoning.
Looks like they have fixed theirs as well:
Your name server, at 126.96.36.199, appears to be safe, but make sure the ports listed below aren't following an obvious pattern.
Requests seen for 73f58c44c681.toorrr.com: