OpenDNS As Quick-Fix To DNS Patch Dilemma
CWmike writes "It turns out that problems with the July 8 patch that was rolled out to fix a cache poisoning flaw discovered by researcher Dan Kaminsky are causing headaches for admins. Preston Gralla suggests a 30-second quick-fix, perhaps until everyone is patched up: Use OpenDNS, which has been patched, as your personal DNS. If you run a corporate network and need help getting OpenDNS set up, your best bet is to go to the OpenDNS FAQ page, he writes."
If you run a corporate network and need the FAQ page to help, you should not be running a corporate network.
Then your job should promptly be given to me.
but how does this stop us from being exploided by upstream dns servers?
Quick everyone - all of our eggs in the OpenDNS basket!
Just a bit ago my parents bought a new router JUST so they could install OpenDNS to protect me from porn... for once I'm actually glad that did it =P
"Our country is not nearly so overrun with the bigoted as it is overrun with the broadminded." -Archbishop Fulton Sheen
So we can replace possible random DNS hijacking with guaranteed DNS hijacking that's passed off as a feature.
Didn't we get extremely upset at Verizon when they served up adverts and returned bogus DNS responses on domains that don't exist?
Seriously, this solution has been posted in response to every DNS article on Slashdot this past month and has been mentioned by just about every article talking about the issue.
Does Slashdot really need to post links to Computer World that rehash was has been discussed 100 times already?
ÕÕ
I did because Comcast is the only service provider in my area, and OpenDNS actually provides better DNS reliability than Comcast's DNS servers. The switch was actually driven by a Comcast DNS outage.
The ringing of the division bell has begun... -PF
Given the near fanatical privacy concerns on Slashdot, I'm surprised nobody is screaming over this "recommendation." Imagine how valuable it would be to know every web site visited by "millions of people a day." Does anyone think the for-profit company isn't mining then reselling the lookup->client-ip information?
On a technical issue, how effective is their service? I've had hotel/hot-spot links that were proxying DNS queries regardless of my settings. It seems to me that unless you know that your ISP's DNS is way broken and that they aren't intercepting DNS queries, this is of questionable use.
No.
OpenDNS does terrible NX-overriding and other useless, annoying things (logins, etc..)
Instead, just use public, geo-distributed DNS servers which FOLLOW RFC and are patched. Here are the standard suggestions (Level7):
4.2.2.1 through 4.2.2.6.
These have good randomness and are multi-cast addresses for DNS servers all over the country. They are VERY fast in most areas.
Oh, and while not naming em, let just say I have a screenshot from long ago that I took from a trace route to Google that I did, and all of the routers that my ISP owned on the way had been renamed to something like "xyz-cannot-secure-their-routers.xyz.com" and such things. Nuff said :)