DNSSEC...not a bang but a whimper?
Tonight is the night that DNSSEC is enabled between the DNS root servers. I am not going to go into detail since the good people at the other ISC have already done a wonderful job of that in their posting.
Lots of the usual hype in the usual places including The Register, slashdot, etc. The fact is that this really only affects the way your ISPs talk DNS to the root servers. I suspect most users are using their ISPs DNS servers which will continue to talk to their customers the old way. It may cause problems for some users who are hosting their own DNS servers behind antiquated firewalls, but for the most part this will be a non-event.
What I find interesting is that using the resolver test at RIPE, my OpenDNS provided resolvers fail.
Hopefully that will be fixed before the big event.
Update: OpenDNS responded to my query with a pointer to a forum article. It seems they are just fine.
-- Rick Wanner - rwanner at isc dot sans dot org
Comments
mike
May 5th 2010
1 decade ago
Windows 2003 SP2
Added HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters
EDNSCacheTimeout DWORD 3600
EnableEDNSProbes DWORD 1
(As suggested by Help > Modify EDNS0 configuration)
After doing so (and restarting the DNS service), the test program failed:
Error
I was unable to run the test because of an internal software error. This could be caused by restrictions of the Java virtual machine on your system.
The test did NOT fail prior to these changes.
The registry change was reverted (deleted the two new DWORDs) and the "Your resolver was only able to get packets SMALLER than 512 bytes." message was again received by the test program.
Exception
May 6th 2010
1 decade ago
Danster
May 7th 2010
1 decade ago