Slashdot Mirror
Verisign Plans DNS Changes
NetWizard writes "According to a recent NANOG post and an InfoWorld story, 'Verisign will change the serial number format and "minimum" value in the .com and .net zones' SOA records on or shortly after 9 February 2004'. They seemed to have learned their lesson, from the post: 'There should be no end-user impact resulting from these changes (though it's conceivable that some people have processes that rely on the semantics of the .com/.net serial number.) But because these zones are widely used and closely watched, we want to let the Internet community know about the changes in advance.)'"
God damn it ICANN, you need to take away Verisign's authority over DNS. Every time they change something it's a major pain in the ass for anybody that works in an ISP, web hosting, etc.
STOP FUCKING CHANGING THINGS!
2038 anyone?
This looks like a good change to me. I can't imagine there would be an outcry over this if Verisign hadn't previously implemented the SiteFinder dung.
With a TTL of 15 mins you have to generate a new zone 96 times a day to keep the zone visible during a whole day. I wonder if they want to speed up propogation time of new domain with this?
To be honest, this makes reasonable sense to me. I can see the case for Verisign wanting to make new registrations available immediately, rather than at the next 12-hourly update.
.COM or .ORG changed, with no real impact on the end user (because of DNS caching). The zone data could even be generated dynamically, directly from a database, with the serial set to the last time the database was updated. I know, historically, this isn't the way DNS servers have worked, but why not run a DNS server directly from a database? This would pave the way for that possibility for Verisign.
.COM/.ORG, there should be minimal other effect, and does make it possible for faster (or let us say 'almost immediate') addition/removal of domains to occur.
Eventually, the zone data could be updated every time the contents of
With the exception of this one-time hit on people who want to pretend to be slaves of
The boxes have to sit on someone's desk. "The community," disorganized and disparate as it is, is remarkably poor at doing anything. You'd have to invent some sort of hierarchy. Maybe have a General Manager of the Internet, and he could have a board of directors under him or something. They would be elected by the nation's population at large, and they'd have the final say on internet issues.
But it's be silly to give EVERYONE an equal vote in their elections, as the great majority of people have no clue how the internet works, and the campaigns for these positions would be totally unable to focus on real issues. They'd have to dumb it down and sugar-coat it so that sixpack joe can digest what they're saying, and at that level of simplicity, who could tell a good candidate from a bad?
Okay, so let's find some way of making sure only highly competent people can vote. We can't give a test, since we'd need someone to create and administer it, and the potential for corruption is too high. The only thing I can think of is selling the votes: that way, every vote is going to represent an informed citizen. After all, who would buy a vote if they don't understand the technology?
So at the point where we've got a CEO, a Board of Managers, and an equity market, we may as well package the whole thing as a corporation and name it VeriSign.
Where in ISO-8601 does the NN fit in? It doesn't.
The time/datestamp should have always been this way; more to the point do you know of any other TLD that at least attempts to be this communicative? They don't do this because ICANN, or anybody, makes them.
.NAME ("oops, we were rooted") or .PRO ("Hi ICANN, I know we said we wouldn't sell SLD name but we're dying here, and we ask a second time can we sell SLD name pleeeeeeeease?") or .biz ("home of more spam since 2000! Yeah baby!!") or any of the cctlds that have (cough) lame servers.
.WS did it 3 years ago.
How bout
Bitch at NSI all you want, they're still the model of a well, if not best run TLD.
And spare me the crap about sitefinder, 22 other tlds did this long before NSI did,
It's reasonable to whine when they do a bad thing (like agree to ICANN oversight, you folks have no idea how close they were to the, um "alternative") but for things that have little or no effect you're reacting to the corporate name not the actual change.
So, put NSI under greater ICANN control? NOT. Frankly we'd be better of if they put ICANN under NSI control.
Hey, is this one of those thigns you can't say because it's hersey?
"Duh. Double duh." - Weemba
Need Mercedes parts ?
It's amazing how well your comment translates to the current situation in America when you change just a few words here and there:
The laws have to sit on someone's desk. "The community," disorganized and disparate as it is, is remarkably poor at doing anything. You'd have to invent some sort of hierarchy. Maybe have a President, and he could have a Congress beside him or something. They would be elected by the nation's population at large, and they'd have the final say on law making issues.
But it's be silly to give EVERYONE an equal vote in their elections, as the great majority of people have no clue how the government works, and the campaigns for these positions would be totally unable to focus on real issues. They'd have to dumb it down and sugar-coat it so that sixpack joe can digest what they're saying, and at that level of simplicity, who could tell a good candidate from a bad?
Okay, so let's find some way of making sure only highly competent people can vote. We can't give a test, since we'd need someone to create and administer it, and the potential for corruption is too high. The only thing I can think of is selling the votes: that way, every vote is going to represent an informed citizen. After all, who would buy a vote if they don't understand the government systems?
Anyway, the serial number is just a revision number intended for the DNS "system" (I'm being a little vague here) to know when a SOA record has changed. There are no end-user servicable parts inside. No human but the people directly handling the coonfiguration of that record needs to know about it - including how it is formed, if it is following specifications. Period.
Sure, if you have build your company based on that tool that tells people when a .com domain SOA record was last changed, you are fucked - for about that minute it takes to change the conversion from int->decimal string->date to UNIX timestamp->date.
Maybe all those complaining are using Windows, and they fear that it may actually take them a day to Google for a routine that does that, and they lose the competetive edge to those UNIX weenies? Sounds like what MS had to say about the Apple/HP iTunes/iPod deal.
Lars T.
To the guy who modded me down from perfect to terrible Karma - Apple haters still suck