Verisign Speeds Up DNS Updates 131
Changeling writes "According to Matt Larson, a representative of VeriSign Naming and Directory Services, on September 8, 2004 Verisign will be switching from performing 2 updates per day of the .com and .net zones to performing updates every few seconds. According to Matt, 'After the rapid DNS update is implemented, the elapsed time from registrars' add or change operations to the visibility of those adds or changes in all 13 .com/.net authoritative name servers is expected to average less than five minutes." Full story can be found here."
I wonder what brought this on? (Score:2, Insightful)
it's not clear to me... (Score:5, Insightful)
The same seems to be true with making DNS changes (new IP address, etc). However, doesn't that mean they will have to adjust the TTL value of the domains all the way down to 5 minutes, which will raise the number of queries skyhigh compared to what they are at now? (Thanks to caching)
Domain Name Portablity... (Score:5, Insightful)
So... the main barrier for switching web hosting providers has just fallen away.
As a consumer (Score:2, Insightful)
Glad to see Verisign can do something right for a change.
On-Demand Update? (Score:2, Insightful)
This might save unnecessary traffics, similar to a hub vs a switch?
Glad to see Verisign coming up to the times (Score:5, Insightful)
Re:Domain Name Portablity... (Score:3, Insightful)
Re:Die script kiddie (Score:5, Insightful)
I doubt it. If an ordinary web browser can find the site, then a zombie could too.
Re:Actually, IP Addresses COULD be portable... (Score:1, Insightful)
Re:Err.. (Score:2, Insightful)
Now, however, you can leave, it will mean lower hosting prices for everyone. Not to mention, having a process be more efficient is always a good thing, even if to the average person it seems to make no difference.
Re:Domain Name Portablity... (Score:1, Insightful)
Dns. I don't think that word means what you think it means.
hint: look at the real reason why it sometimes takes days when you make a change, and you'll realize that it has nothing to do with verisign or root servers.
Re:Thanks, Verisign... (Score:4, Insightful)
You can lower the recommened caching timeouts on your own DNS server. So if your ISP changes the IP of your web server other's DNS servers will request the data from your's again sooner. But of course this can place a higher load on your DNS server.
What happens in 2038?! (Score:3, Insightful)
"these serial numbers are now based on UTC time encoded as the number of seconds since the UNIX epoch (00:00:00 GMT, 1 January 1970)"
Uhh, call me stupid, but isnt this the kind of moronic thinking thats gonna nail us AGAIN in 2038 when 32bit epoch dates roll over?! Does anyone know if bind can handle 64bit numbers for serials? Or is this just another screwup waiting to be discovered in 2037 just before the internet stops working cause all the DNS servers cant handle > 32bit
With everything else as instant as it is... (Score:1, Insightful)