Slashdot Mirror
DNS Root Servers Outside US Surpass Those Inside
penciling_in writes "Paul Rendek, head of member services and communica of RIPE Network
Coordination Centre (RIPE NCC) has
reported on CircleID that: 'For the first time in Internet history the
number of instances of DNS root servers outside the United States has overtaken
the number within. The balance was tipped by the recent launch in Frankfurt of
an anycast instance of the RIPE
NCC operated K-root server.' In
the same report, Daniel Karrenberg, Chief Scientist of the RIPE NCC says:
'We monitor the quality of the root name service from more than 50
locations worldwide, and we publish the results for everyone to see.'"
So it was a K-raut K-root server that tipped the balance?
*dodges the thrown fruit*
The number of countries outside the U.S. outnumber the number of countries inside the U.S.
I just changed bloody hosts three days ago and my DNS still isn't completely changed over! Now I find out it's because all the new servers are farting around in Frankfurt! Great, just great! =)~
My Webcomic: Asylum on 5th Street
Sure, there may be more DNS root servers outside the US, but it would seem that Verisign still has exclusive rights to muck around with them. So what's the big deal?
"Service quality and security is not always proportional to money spent."
Time until someone makes a Windows-Linux parallel: 5... 4...
The coolest voice ever.
I'm an American, and I love the US, but the imbalance of the internet towards the US has always bothered me. To me, it always has seemed that it should be a completely global venture, and be supported fairly evenly throughout the globe.
DNS servers are probably a good indicator of internet usage/participation and the fact that other countries are catching up is a good thing; however, just shy of half of the DNS servers are still in the US. That's pretty sad considering we represent less than 5% of the global population. Here's to hoping other countries continue to grow in their participation.
Also, I hope Babelfish improves as globalizations continues.....
I am part K-raut you insensitive K-lod!
It is easier to build strong children than to repair broken men. -Frederick Douglass
"Personally, I'm torn between the cushy redundancy offered by decentralization, and the cushy security of having most of the servers in a stable, well-protected country."
oh i forgot, germany is such an unstable rogue state. better hurry up and invade!^H^H^H^H^H^H liberate
I'll just use my special getting high powers one more time...
Quick...
/. THAT
Everyone ping k.root-servers.net and try and
... and then there were none
I'd hate to think any of my packets being exported to those guys who wouldn't even help us rid Iraq of weapons of mass destruction! I think in protest, we should hereby refer to all the USA DNS root servers as "Freedom Hosts" (cue Lee Greenwood music...now).
If all the root servers somehow miraculously disappeared then most people would be alright for 1-2 days. After 2 days all the cached NS records for .com will have expired and virtually no one will be able to resolve any .com addresses. Similar results for all other TLDs, but the time until resolution failure for each TLD can differ.
Of course this is a highly unlikely scenerio as there are 13 root DNS servers and many of these servers are actually multiple machines using anycast (for example). Of course, taking out a handful of the machines places sufficient load on the remaining servers to cause them to start dropping requests, but this too is unlikely.
My Company
I think you're confused. The Germans volunteered to change the names of things such as saurekraut (I'm only half German) to "Liberty Cabbage" during WWII because they were getting persecuted so much by (you guessed it) Americans. We Americans know that the French are too stuck up to stick it to themselves so we changed "their" things to names like "Freedom Toast." And I'm not old. I learned that "Liberty Cabbage" thing from Grandpa Simpson. I kid you not. Simpson's is edumacational.
And besides, even the govenment couldn't change the name to "Freedom Hosts" because even they are slaves to VeriSign. It'd be all wrapped up in too much irony. Even for this administration.
Source
Ben
Work Safe Porn
In the bad old days you and you alone were in control of name resolution. For those of you without receding and/or grey hairlines who may not know or remember this, you had a file called hosts.txt that contained all the mappings of names to IPs. That, obviously, didn't scale and DNS was developed and was widely deployed by about 86 or so.
The one big gotcha with DNS is it takes control out of your hands. That is, you may have your own DNS server locally, but you traditionally refer to other servers that serve up the root zone that tells your DNS server where all the TLD servers are. Somewhere along the line the decision was made to use other machines, not your own, for this.
This is wrong for many reasons:
But there are ways around this. The easiest if is you static route the 13 root server IPs to your own nameserver. Then you can run an unmodified copt of the legacy root zone on your own nameserver and the US government root servers can be backhoed or DDOS'd and you wouldn't even notice. ISP's are starting to figure this out, especiallly ones with expensive longhaul connections.
Or, you can modify your nameserver to declare youtself primary for the root zone (which you've dutifully downloaded) and edit out the declarations for "." in the legacy root zone.
Or you can use the ORSC root zone. If it's good enough for two ICANN board members, it's good enough for you.
Whatever you do, for God's sake dump bind and use DJBDNS. It really is so much better it's just not funny.
Need Mercedes parts ?
Those numbers don't change,
They can, and often do.
How often do calls to the "root server" get made
Many millions of times an hour. Each zone (or domain, in practical terms) has expiration and refresh times. In addition to caching host and other data, these expiration (ttl) and refresh times get cached as well. The clock is ticking on the ttl when first cached, and when it expires a new lookup will have to be made (even if the resulting information is, as you said, identical, e.g. it "doesn't change") Just about every time a lookup is made by a tier 3 name server the query will recursively end up at a root server which will point it back down to a gTLD server and down to the tld auth server which finally sends the data to the requestor.
Or something like that
http://www.cbc.ca/mondayreport/videos/ontario.html
Need Mercedes parts ?
what they are talking about for a change.
The recent flurry of articles giving the impression that VeriSign is somehow "in charge" of DNS has been rather irritating, when in fact, it is not difficult to configure your DNS server to ignore VeriSign operated root servers. (If you're using bind, dont include thier roots in your roots.cache zone file. I'm sure there's an equivalent trick for djbdns.)
I wish all of those who are about to continue the current flood of "what difference does it make?" and "VeriSign controls DNS anyway." posts would kindly read this article and this one as well for a breif tutorial on DNS from that programmer who writes good shit but everyone says they hate him anyway, D. J. Bernstein.
If you like the subject, maybe you should go out and buy a copy of DNS and BIND so you'll have something interesting to talk about at the coffee house this weekend.
The truth is that DNS is a distributed system that is rather well designed to be redundant. The anycast implementation mentioned in the article is a good and needed way (it's the right way[tm]) to increase the redundancy that is already inherent in the system, making DNS much more secure and resistant to DDOS attacks and other attempts to disrupt DNS service. VeriSign showing off thier "secure" sites, and blowing thier own horn about how "important" they in particular are to the internet is a load of sh*t that should not be given a second thought unless you are in the habit of educating our lawmakers about related issues. Not an especially good habit, it will make you enemies (but only if you're right).
Read, L