ICANN Asks VeriSign To Stop DNS Wildcarding
MrClever writes "In this article over at the Sydney Morning Herald (AU), it looks as though ICANN may actually be doing something about the VeriSign changes to .com and .net TLD's. Apparently, while they have been noticably quiet, they have been reviewing community reaction and analysed data from a technical perspective. Here's hoping ICANN pull the plug on VeriSign's TLD administration rights!" And TALlama writes "RSS.com.com (dear $DIETY, will it ever stop?) is reporting that ICANN has asked VeriSign 'to voluntarily suspend the service' of wildcarding DNS, 'pending further study.' Calling it a 'service' is a little bit of a misnomer. If I punch people in the face, can I call that a service, too?"
There was a great story on slashdot about it the other day.
Mouse powered Chips, Open source Processors and Lego
If the people you are punching are the one responsible at VeriSign for the SiteFinder "service", I would call it service for sure.
Do I point out the earlier thread, or do I repeat the major points from it for extra karma?
Verisign broke the DNS RFCs, abused its position as keeper of the root servers, we'll never trust it again and they should be replaced, distributed DNS servers, let's all install the BIND update in the meantime yada yada.
At least it looks like the post was spellchecked.
Strange women lying in ponds distributing swords is no basis for a system of government.
You must be new, this is a new feature of Slashdot. It's there just in case you didn't see the story the first 5 times.
Attempt to be funny
Your hair look like poop, Bob! - Wanker.
VerySign have already brought that domain-name! verysued.com resolves to VeriSign's own servers (64.94.110.11)
Sure it is. and for this you'll serve time in a prison!
This