The Root of All E-Mail
wiredog writes "A Washington Post story about the DNS, the VeriSign NOC, and some of the security therein." Especially interesting in light of the recent security lockdowns throughout much of the Western world. The havoc of losing the A root server would be bad, like Staypuft Marshmallow Man bad.
Obscurity is the first line of defense. The building is unmarked, its address unspecified in company literature and its managers tight-lipped about disclosing driving directions or identifying markings to strangers.
They are apparently okay with featuring the place in an article in the Washington Post, though. Sheesh.
I watched C-beams glitter in the dark near the Tannhauser gate.
Reading about the physical security is interesting. I'm wondering why they wouldn't just contract out with the Government and move the operation to a secure military installation somewhere in the DC area. There are plenty of them around there. Granted, it seems that they have taken care of their current security needs, but it might be cheaper/easier to locate it in a protected area that is already guarded. I get the feeling that "Security through Obfuscation" (the actual building) might not be the best policy.
Still fascinating though.
Jason
He's totally creeping out the Great One, eh...
Security through obscurity will never solve anything when used as the first line of defense.
If you're going to build a place like this, someone unauthorized will eventually find out about it. Hell, just look at the security of the government's nuclear research labs and the whole Wen Ho Lee fiasco a few years back. And nuclear secrets are far more dangerous than a temporary internet slowdown.
If I was them, I'd quit worrying about how plain looking and unmarked the building is and start worrying about how hardended it was made. Ideally, they would place it inside a mountain so it would be immune to various airliners falling out of the sky. Also, it would have a myriad of redundant network links.
Secrets have never worked in security before, and they won't work now. If they want to protect the root servers, they'll have to base it on sound engineering, not the assumption that no one will ever find which building it's located in (any network engineer with a sense of adventure and a flashlight can prowl the sewers tracing data lines, anyway.).
is Dogbert the CIO at Verisign or something?
"He who controls the information controls you. I CONTROL THE INFORMATION!!"
"Obscurity is the first line of defense. The building is unmarked, its address unspecified in company literature and its managers tight-lipped about disclosing driving directions or identifying markings to strangers."
Hmmm....
VeriSign Network Operations Center
21345 Ridgetop Circle
Sterling, VA 20166
I don't think security is *quite* as tight as they say. Course, if A root where to go down, I wouldn't know the difference betweent that and the crappy windows DNS servers here....
Venkman - "I'm a little fuzzy on the whole good/bad thing. What do you mean, bad?"
Egon - "Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light."
Ray - "Total protonic reversal..."
Venkman - "Alright, important safety tip. Thanks, Egon."
Ah, one of the great comedies of the 80's...
---
"how can the same street intersect with itself? i must be at the nexus of the universe!" - cosmo kramer
Hemos said...
Especially interesting in light of the recent security lockdowns throughout much of the Western world. The havoc of losing the A root server would be bad, like Staypuft Marshmallow Man bad.
Absolute proof that the Slashdot editors don't even bother to read the articles, and just depend on their wrong understanding of things.
From the article...
"The DNS is built so that eight or more of the world's 13 master root servers would have to fail before ordinary Internet users started to see slowdowns, according to John Crain, manager of technical operations for the Internet Corporation for Assigned Names and Numbers (ICANN).
ICANN manages the DNS and sets policies for registry operators and domain name retailers.
"Theoretically, if 'A' were to disappear, we could pick it up from one of the other servers," Crain said. "Moving the place where the zone is picked up is very simple."
In other words, don't panic. The A server is just the highest profile target.
Sometimes it's best to just let stupid people be stupid.
The article seemed to be a little scare-mongery, considering how they go on to describe that the other root servers can easily take over.
A bigger question is: how well protected are the public peering points, like MAE East and MAE West? Since even international traffic is often routed through them, we would see an instant slowdown if one of those two nerve centers were destroyed. Big businesses might have private peering arrangements that would survive, but you can bet that a ton of smaller sites would be affected by a loss of a MAE.
Your right to not believe: Americans United for Separation of Church and
The slashdot post is misleadingly sensationalist (I know, shocking!)
The article states that 8 of the 13 root servers (which are located throughout the US) would have to fail simultaneously before internet users would even notice something was wrong. I think that qualifies as "a little redundancy"...
Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
Actually, the article states that the redundancy does exist, and that the A root server is not really a target; 8 or more of the 13 master servers located around the world would have to be taken out before internet users would even begin to notice.
Out of curiosity, I've seen pictures of lots of NOCs that have similar setups as what's described in the article. What kind of software is usually used for putting real-time "war room" statistics up on NOC displays? Is it usually custom-written for each setup?
Weirded me out the first time; now I'm pretty much used to it. It's really weird when you're hiking the Appalachian trail. But that's an entirely different story.
Hmmm, the article seems to make a BIG point out of the fact that losing the A root would be non-catastrophic. Indeed, they mention that 8 of 13 roots would have to be down before the average user would notice the slowdown. It's nice to know the users here aren't the only ones who like to post without reading the article.
But the article further goes to mention how important the Internet is to our economy. Is this true?? I don't really think of the internet as critical infrastructure.
If the Net went down tomorrow, and was down for a week, would this really affect the economy in a signifigant way?? (Well, aside from the panic of investors...)
I understand that more and more comapnies are using the Net in a part of their workflows, but I don't think the internet provides and unique service that couldn't be done without.
E-mail: Use the phones.
Web: Read a book
Any data that is transferred could just as easily go by modem.
The internet serves as a convenience in many ways, but I dont think this almost 10 year old (less in the corporate mind) bit of infrastructure has become crucial to us yet. It has really been just the last few years that anybody started doing anything with the net at all, and mostly that has been VPN and changing communication methods. (i.e. Use the net instead of UUCP and a modem.)
So, my question is, what kind of critical services would be missing if the net suddenly went away. Sorry, I do not consider e-mail a critical service.
~Hammy
nothing4sale.org
IN AD 2002 WAR WAS BEGINNING
(Scene: Verisign Data Center inside Washington DC. Huge explosion on top floor of red brick office building, sending flaming servers flying through the night sky)
(Cut to home of Verisign CEO, he is in bed with his fat wife, snoring loudly. The phone rings, and he wakes up, wiping the slobber from his chin while answering)
Verisign CEO: "What you want!"
Voice on the phone: "Somebody set us up the bomb!"
CEO: "What you say!"
Phone voice: "We get signal!"
(static on phone, all of a sudden a voice breaks in)
Arabian voice: "How are you gentlemen? By the Grace of Allah, All your A Root Servers are belonging to us! You have no chance to survive, make your time!"
CEO: "It's YOU! Restore backup! Implement Emergency Response Plan A! Move every server! For great justice!"
Arabian voice: "HA HA HA HA HA HA HA!"
mje0w!!!1!
You need to read RFC 2870.
--
Mod up a post Rob doesn't like and you'll never mod again
The DNS system is probably one of the least problematic systems. The zone files that are spread out to the root servers are also "publicly" availiable. No, you can't get them (would be a problem because of spam, etc.) but ie. large ISPs can get them to run their own root level hiearchy. This is good for large ISPs as it will cut down on bandwidth usage. This might also be a great solution for the future. If ISPs hosted the root level zones themselves, the DNS system would be virtually unbreakable and the bandwidth usage due to DNS requests would dissapear.
The last thing I'd want someone to think is that they could put a bomb around their waist and hug the A root and think they're going to significantly impact the Internet," Rippe said.
Rippe said that while such an attack could kill many employees, the Internet's addressing system is designed to withstand the destruction of much of the physical infrastructure that houses it.
So the threat of someone cracking the DNS server and screwing it up in such a way that it wouldn't get noticed immediately could be worse. Let's say you start altering the records. Once that starts to replicate from the root server on down, you can cause a lot of trouble. Do that to just eBay's or Amazon's domain (or gasp! Slashdot's), and you could cause quite a stir.
Robotiq.com is heavily tested on animals
"Obscurity is the first line of defense. The building is unmarked, its address unspecified in company literature and its managers tight-lipped about disclosing driving directions or identifying markings to strangers.
While the location of the building is not a true secret -- dozens if not hundreds of Internet addressing insiders know where it is -- it would be difficult for a casual vandal or criminal to stumble across it, Rippe said.
And the casual vandal or criminal would be interested in it because?
For crying out loud, a 1 second Google search on "Verisign NOC" reveals the COMPLETE ADDRESS in a PARTY INVITATION!?!? in the very first result!
Yeah, I feel safe.
I have a world map with root-servers pointed on it, looks like the area in which the A server is (Virginia, Maryland) hosts not one but six (A, C, D, G, H and J) servers, some of which (like H, run by US Army) are probably veeery well defended...
I found a link to the same pic on the net:
cs.ucla.edu
...or maybe just nuke the whole area and you take down 6 of them
Vacuum cleaners suck. Kings rule.
DNS is already distributed. You're friendly neighborhood ISP caches the most often used DNS info, and 80% of internet traffic is resolved there. Only a small portion of traffic has to be escalated to a root server. That's why, as the article said, 8 of the 13 root servers would have to be taken out simultaneously for users to notice any slowdown. An attack on the A root server would be more symbolic than actually damaging. Even if it was done by the Stay-Puffed Marshmellow Man.
Don't forget that Friday is Hawaiian shirt day.
"The DNS is built so that eight or more of the world's 13 master root servers would have to fail before ordinary Internet users started to see slowdowns, according to John Crain, manager of technical operations for the Internet Corporation for Assigned Names and Numbers (ICANN)."
Where did this magic number 8 out of 13 come from?
-- everyones not everybody and neither is everybody like everyone.
As briefly noted in the Post article, the DNS infrastructure, like most essential net technology, pretty much doesn't have any single points of failure. It's immune to local physical attacks or natural disasters. The article is just a sensationalist trip into a modern high security datacenter full of Ooh-ing and Aah-ing, and doesn't have much relevance at all to the security or stability of the 'net.
11*43+456^2
I was thinking at least round-robin DNS cluster but it seems like A root server is just one box. I'd worry about hardware failure more than terrorism if it was just ONE machine running the zone. What kind of hardware does the A server run on anyways?
There's 10 types of people in this world, those who understand binary and those who don't.
It was stated that if 8 of the 13 root servers were destroyed, the internet would slow down?
Ummm... no. It wouldn't slow down. DNS resolution would stop. Thats it. Most users might think the entire internet came to a complete halt, but thats not the case.
Skiers and Riders -- http://www.snowjournal.com
So.. let me get this straight. Verisgn realizes that they basically "run" the internet and as a result they don't care if they blow customers off. I'm sure I'm not the only one who has had major issues with Verisgn. Even writing to them for a simple answer to a simple question about how often domain names are flushed from their database results in them coming back to me with a request for more information. I ask them
"> How often do you guys "flush" your database so
that expired domain names
> become public again? There are some domain names (even ones I've owned
> but not renewed that after a year are still in the database)."
and they say:
"Please know we genuinely want to help you in this matter.
In order for us to assist you please send the following to:
customerservice@networksolutions.com
a) A detailed description of your concern or question
b) The domain name
c) account number (if applicable)
d) Any NIC tracking numbers you may have received. These
appear in the subject line of the header of all messages
sent from VeriSign (example: NIC-010409.3ee1)"
What Ever! I included more then enough information in my e-mail. Perhaps the fact that Verisng is "god" of internet domains and NSI is the reason they haven't expired domains that have expired since 1 - 1 1/2 years ago!!!?!?
If someone should be able to knock out all these root servers, zone-files and the major DNS's in the world the net would still excist. In the days to follow such a thing hackers would start running DNS-servers, searching logs and reconstruct the domains. Following weeks governments world wide would have reconstructed the net on more solid bandwidth.
Look a monkey!
Just FYI:
:-)
The root-servers know where to find everything which is below the root (like com, edu, net, nl, au, cn, tw, us).
The gtld-servers (global top level domain, i.e. the non-country codes) know where to find everything which is like philips.com, freebsd.org and berkely.edu.
The country-code-servers know where to find xs4all.nl, org.au and co.uk.
In the past I've made a small tool called dnstracer (shameless plug) which shows you what queries your DNS server is doing to get the answer for a hostname.
If you play a little bit around with it you'll see how easy it is to live without connectivity to the root-servers.net machines, thanks to caching etc. Well, for the first two days that is
bash$
In any security situation all you would need to find is the weakest link. It doesn't matter how well that building is protected it needs to comunicate with the world and therfore this issue is more complex than it sounds.
DRM? No thanks, I'll just get it somewhere else...
You mean, put a sign inside the building that says "By opening that door a few minutes ago, you agreed to be shot."
"Patriotism is your conviction that this country is superior to all other countries because you were born in it." -- GBS
Once upon a time, the MAE NAPs were certainly a big choke point. A few years ago, you could have blown up two nondescript buildings across the street from each other in Tyson's Corner, VA (MAE-East 1 and 2) and a tall building on Market Street in San Jose (MAE West) and pretty much taken down the Internet.
However, that's not so much the case today. The fact is that most traffic (in the US at least) goes between the Big Three (UUNET/WorldCom, Sprint and Cable & Wireless), or at least it could go because most networks have an upstream multihomed connection to one or more of the big three. And those guys have plenty of private interconnections, some of which are outside of the NAPs.
Networks have also shifted away from the old MAE model (FDDI connections into these huge mother-f***er DEC gigaswitches housed in the MAE buildings) and towards ATM-based NAPs, where you just get a virtual circuit in a "cloud" in the area. The weakness of the FDDI-gigaswitches model that caused people to move away from them was not the security aspect, but rather that they were a huge pain to upgrade and became a huge sinkhole for packet loss when they were overburdened (e.g., MAE-East in late 1997).
Of course, the MAEs still are important - there's a hell of a lot of fiber running through there, and taking it out would require everyone to route around it, causing a HUGE temporary disruption - but they're not the tremendous choke point/security risk that they once were.
"95% of all Slashdot
"The last thing I'd want someone to think is that they could put a bomb around their waist and hug the A root and think they're going to significantly impact the Internet,"
Forget the bomb. What techie wouldn't get a boner for the chance to "hug the A root"?!?
I'm against picketing, but I don't know how to show it.
You are absolutely right. It's aboot freedom. It's aboot security. It's aboot obscurity. It's aboot time we move this thing to Canada!
Moon Macrosystems. Sun's biggest competitor.
The havoc of losing the A root server would be bad, like Staypuft Marshmallow Man bad.
Psh! I don't care if all DNS servers collapsed! I've got 64.28.67.150 tattoed on the back of my hand.
Pinky: "What are we going to do tomorrow night Brain?"
Brain: "I would tell you Pinky but this 120 char limi
[Your] friendly neighborhood ISP caches the most often used DNS info, and 80% of internet traffic is resolved there...That's why, as the article said, 8 of the 13...
Actually, the reason you'd have to take out 8 of the 13 has nothing to do with caching. It's because the root DNS servers MUST be able to handle three times the peak traffic of any one server at any time; that is, normal traffic, with all servers operating, MUST never exceed 1/3 capacity of the server in question. This is part of RFC 2870, the RFC that specifies operational details for the root servers. The RFC specifies this level of capacity to provide for redundancy; that capacity means that we can lose 2/3 of the servers without overloading the remaining boxen. 8 is just a shade less than 2/3 of 13, so that's where we get the number.
(Grammar correction mine.)
"Make it ten--I am only a poor corrupt official."
--Captain Louis Renault (Claude Rains), Casablanca
Why would terrorists want to attempt to destroy or cripple the Internet? It would be naive to think that they do not use it for communication and information. I could be wrong, but to me it would not make sense for them to try and destroy or harm the Internet as a whole.
Attacking portions of the Internet might make more sense, but I still do not think that terrorists would try to destroy or criple extremely vital portions of the Internet that affect it as a whole.