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.'"
Last time I checked, Germany is .de. .dk is Denmark. As for why some ccTLDs are derived from the local language (.de, .es) and some aren't (.jp, .ru), your guess is as good as mine. (One theory is that countries where the local language uses a non-Roman alphabet (or no alphabet at all) got their ccTLDs derived from the English names for those countries.)
20 January 2017: the End of an Error.
Many hosting companies, etc. use shared servers. I do as well, in fact, for my websites. For example, my website www.studentprogress.info may have the IP address 65.49.199.172, but the site will only show up if you use the hostname.
Based on the sheer number of websites these days, I'm sure we'd run out of IPv4 space instantly without DNS, and maybe even run out of IPv6 space!
There's no place like localhost
As i stated in the past the only reason verisign, ICANN or anyone else has DNS power is because everyone agrees to use their standard.. well.. not everybody ;) there is a choice in the matter anyone who wants to run a DNS server can do so and can map domains to whatever IP address they like... it's just that issuing conflicting domain names on different servers benifits nobody and makes things worse for everyone
Snowden and Manning are heroes.
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
Just like telephone networks, automobiles and transistors the internet will follow the usual pattern of: 1. US Invents it
Except the US did not invent the autombile.
The most significant contribution the US has made to automobile engineering is the cup holder.
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
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
I've been using the ORSC root zone and its servers for several years. I have not noticed any outages or problems - oops, yes there was a problem once - it was when ICANN decided to create a .biz of its own even though there was one already running.