Slashdot Mirror


Inside the Rise of the Domain Name System

Greg Huang writes "Looking back, it's almost impossible to believe that for most of the 1990s, a single company, Network Solutions, had a government-issued monopoly on registering domain names on the Internet. And considering how central the company was to the growth of the Web, it's surprising how little of the company's back story — how it got into the domain name business, or who owned it — has been told. Xconomy has an in-depth interview with two former executives from SAIC, the secretive San Diego defense contractor that bought Network Solutions in 1995 for $5 million and sold off the domain registration business in 2000 for billions of dollars."

18 of 74 comments (clear)

  1. Single entity by sopssa · · Score: 5, Informative

    It's interesting that Network Solution was the only handler for domain registration back in 90's and while there are lots of registrars now, they still work under ICANN. Yeah the usual argument in slashdot is that you could always start your own tld, but nobody is going to support it unless you're high in chain, aka ICANN.

    Interesting aspect was a few months ago when EU wanted more freedom from ICANN and its association with US. Currently the internet domain name system is pretty much controlled by one entity, which isn't really the purpose of internet, and its also why Network Solution was taken off the domain registration game as the single player. Monopoly is never good.

    Fact is, currently DNS still relies entirely on *one entity*. It goes completely against the distributed structure of the internet.

    1. Re:Single entity by Shakrai · · Score: 5, Informative

      Fact is, currently DNS still relies entirely on *one entity*. It goes completely against the distributed structure of the internet.

      So do IP address assignments. So do AS number assignments. Why does nobody ever complain about them? If you want something to be uniquely assigned (domain names, IP addresses, AS numbers) then it seems to me that it's going to have to be centrally managed by someone.

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    2. Re:Single entity by sopssa · · Score: 2, Insightful

      So do IP address assignments. So do AS number assignments. Why does nobody ever complain about them? If you want something to be uniquely assigned (domain names, IP addresses, AS numbers) then it seems to me that it's going to have to be centrally managed by someone.

      I would.

      However, IP address assigment is not handled by single entity. Theres separate organizations for north and south america, europe, africa and asia. So you're missing the point there.

    3. Re:Single entity by kwanbis · · Score: 2, Interesting

      I still remember the first time i had to call Network Solutions, for a domain issue. I was given this name, and they picked up the phone, and it was like i had called a person's house. Very unprofessional. And i thought, this must be a mistake, this is "international network", it can not be a private company. It was.

    4. Re:Single entity by Shakrai · · Score: 2, Insightful

      But that someone should be distributed, i.e. a group instead of a single entity

      Why?

      And the systems should be distributed and mirrored too.

      The systems are distributed and mirrored. There isn't a single root server for the entire internet running in ICANNs basement......

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    5. Re:Single entity by ivan_w · · Score: 3, Informative

      I could be wrong but I was under the impression that, actually, IP address blocks and Autonomous System numbers are managed by LIRs which get their blocks from RIRs (like RIPE, APNIC, ARIN, etc..) (except Europe which has no LIR) which in turn get their blocks from ....

      The IANA (Internet Assigned Number Authority)

      And ICANN also gets its authority from IANA.

      So it's not centralized per-se, but it's highly hierarchical

      --Ivan

    6. Re:Single entity by jeffmeden · · Score: 2, Informative

      Fact is, currently DNS still relies entirely on *one entity*. It goes completely against the distributed structure of the internet.

      Fact is, there needs to be cooperation if there is going to be ONE internet. Your argument only stands if there were two entirely distinct distribution mechanisms (physical networks) controlled by one entity. Given that there is only ONE network, it makes sense that at some point there needs to be a top level of control. Without it, you get wrestling for control, dirty tricks, etc. which is just as much a bad thing as is a (transparent) monopoly.

    7. Re:Single entity by jjeffries · · Score: 5, Insightful

      Remember when ICANN routed all unassigned IP space to a helpful web page full of advertisements, breaking many other things in the process?

      Me neither.

    8. Re:Single entity by Unordained · · Score: 2, Insightful

      ... if that means that megacorps also can't go around buying up dozens of extra domain names for no really good reason -- one for every special deal they ever offer, every product, every movie they put out, every ... whatever, then sure. You get what you get, and that's it. But that's not going to happen.

      Trademarks are essentially local. Two companies can even operate under the same name, as long as they're not getting in each others' way, creating confusion -- by being in the same market (by product or area). There's paperwork (and treaties) involved in making those trademarks global. What would make more sense is to get rid of the .com and .gov TLD's and replace those with .co.us and .gov.us . If another country wants to have whitehouse.gov.jp, then fine, let them have it. We have ours. We're not competing on the international scene for the name "whitehouse". (There are many whitehouses, by the way.) If TLDs are aligned with trademark-assignment organizations, we can avoid some (but not all) the weirdness.

      Misspellings: how many products are named with cute misspellings? Who's to say that those are intended to be malicious? If you require someone to have a product first, you'll see CocaCola buying every variant of their name, and preventing anyone from ever naming their product C0k3C0l4, even if they might have initially. So you can grandfather in misspellings, but you then section off a whole range of possibilities just because?

      Aligning with trademark organizations presents problems for small businesses and personal users, who have no real interest in having a globally unique name, but could use a locally unique one. Maybe no product is involved. Other than DNS, you'd have no reason to deal with trademarks. Why should you? The system we have now essentially says "fine, get your DNS name, but if a trademark holder comes along later, we'll screw you" which isn't fair, but does provide a "rule" (ICANN ruling) for determining priority.

      Taking away TLDs just makes it easier for squatters to sign up for names, especially if you automate the detection of misspellings and assign them all to an existing holder. You can kiss creative DNS names goodbye.

      Others can probably clean up and add to my arguments, but the point is ... please reconsider. Ridding ourselves of TLDs doesn't help things. Maybe something else would ... but not that.

  2. Not To Celebrate Network Solutions, But... by damn_registrars · · Score: 5, Insightful

    There was a definite advantage in terms of ICANN enforcement of registrar responsibilities when there was only one registrar. Now that we have hundreds or thousands of registrars, we have all kinds of nonsense going on in blatant violation of registrar accreditation terms and ICANN can't keep up with the problems. Which apparently lead ICANN to their new strategy - nothing. Now we have unscrupulous registrars all over the world selling domains to bogus registration information, making it much more difficult to uncover who is really behind various nefarious acts on the internet (including but by no means limited to spam).

    So in the end, the monopoly was indeed broken up, but the consumer lost, and lost big.

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
    1. Re:Not To Celebrate Network Solutions, But... by Anonymous Coward · · Score: 3, Insightful

      There was a definite advantage in terms of ICANN enforcement of registrar responsibilities when there was only one registrar.

      Take off your rose tinted glasses, please. Have you forgotten the exorbitant charges for domains when NetSol were the only player in town? May not seem like a big deal to a business, but it certainly prevented the internet from expanding as quickly as it could have, but sooner, due to the lack of affordable options to people who were online at the time. I sure as hell would have had my own domain a lot sooner if it wasn't for the fees that NetSol was charging... and everyone knew it monopolic overcharging then.

      Despite the insane amount of money they were charging for domain registration and renewal, their security was worse even then. They didn't even bother to contact people by phone or mailing address before accepting a SPOOFED EMAIL as a valid request for changing domain ownership.

  3. agreed by circletimessquare · · Score: 2, Interesting

    for most industries (consumer electronics), it should be an unregulated or lightly regulated free-for-all. this maximizes consumer value

    but there are certain industries where a regulated monopoly makes sense (electricity grids) and competition actually decreases consumer value

    and then there is a third category: certain industries where a regulated OLIGOPOLY makes sense (cable) and competition beyond a select few actually decreases consumer value, and at the same time dominance by one player decreases consumer value as well

    and i would say that domain names falls into the oligopoly category: there should only be a few domain registrars. choice should be maintained, with all the free market benefits that come with that, but not at the cost of a deluge of seedy anonymous players

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  4. Peer to peer db's? by Anonymous Coward · · Score: 4, Insightful

    You know, I'm not sure some of you people know how the Naming system works. The difference between the Root Zone and some registrars like Network Solutions(at present)are night and day. If you think a single source of accurate data can be distributed between different companies in different nations, you are high. Really, there are so many things you aren't considering that you short start by considering swallowing your tongue. In the end, there can be only one. It's not that they're just so unhip- it's physical reality.

    And I would comment further, but I shouldn't because I actually know what I'm talking about.

  5. Oblig. by rrohbeck · · Score: 2, Funny

    DNS became self aware at 2:14 am EDT August 29, 1997.

    Be afraid, very afraid.

    That said, it's time for distributed secure name resolution. Those name servers are just too easily messed with. There are many approaches, mostly used in P2P, from Kad to Freenet.

  6. BIND security hole - are you patched? by Phroggy · · Score: 2, Informative

    Slightly off-topic, but just a reminder: have you patched the BIND security hole yet? If you're running BIND 9 and your server is the master for any domains (including localhost), and you haven't patched this week, one malicious packet can crash your server.

    If you have a master nameserver on a private network or behind a firewall, and your public-facing nameservers are all slaves with no master zones at all, you're safe. If your infrastructure is set up like that, except you use rsync over ssh to send updated zone files to your "slaves" but they're actually configured as masters, you're vulnerable. Contrary to what you may have heard, it does not matter whether you use dynamic updates (e.g. from dhcpd) or not.

    This firewall rule blocks all dynamic update requests, including the exploit, on recent versions of Linux (but didn't work on any of my DNS servers, because they're all running older distros):
    iptables -A INPUT -p udp --dport 53 -j DROP -m u32 --u32 '30>>27&0xF=5'

    Of course if you're running djbdns or something else, you can continue to be gleefully smug.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  7. Get rid of TLDs! by qazwart · · Score: 5, Interesting

    Get rid of all the top level domains except for the country ones. No more .com, .net, .edu, .org, and all the stupid new ones recently concocted.

    Instead, you just have the country level domains, and allow each country to control their domains the way they see fit. In most countries a domain name would be handled like any other trademark issue.

    In the U.S., you'd eliminate domain name squatting since you must show some sort of actual activity to retain a trademark. Buying "Sporf.com" and sitting on it in hopes that a company called "Sporf" will have to buy the domain from you will no longer be a good business model.

    Will greedy capitalist evil corporations steal your domain? All you have to do is show that you've actively used the domain (and not just merely have a parking page), and that you've registered your trademark with the correct authorities (something that could be done by the domain registrar where you bought your domain).

    In the U.S., domains can be done on a local basis (memphis.tn.us), on a state basis (state.tn.us), or on a national basis (com.us). This way, two local shops called "The Flowerpot" -- one in chicago and one in memphis -- could have the same domain: flowerpot.memphis.tn.us and flowerpot.chicago.il.us. National companies like Apple and Microsoft could get their domains registered as apple.com.us and microsoft.com.us.

    The .com domain could become a virtual domain. You type in a company name with a .com suffix, and your browser will search your local area, then the state, and then nationally for a company with that domain prefix. Thus if I live in Memphis and type in "Flowerpot.com", I get flowerpot.memphis.tn.us. If I lived in Chicago, I get flowerpot.chicago.il.us.

    This would allow us to get rid of TDL sprawl (.name, .info, .biz, .mobi, etc.) that isn't benefiting anyone but GoDaddym It would eliminate all the sniping the the U.S. controls domains because they'll only control the .us domain. And, it would greatly simplify the whole domain registration process.

    1. Re:Get rid of TLDs! by evilviper · · Score: 2, Insightful

      Instead, you just have the country level domains

      Oh good. Then anyone with international interests has to maintain several hundred domains, to make sure they are easily found by people around the world looking for them...

      Buying "Sporf.com" and sitting on it in hopes that a company called "Sporf" will have to buy the domain from you will no longer be a good business model.

      Oh good. Then it'll just be Sporf farm equipment fighting with Sporf housewares, and Sporf online store, fighting it out for control of their mutual namesake...

      And the US government is going to drop everything to make sure our domain names stay clean, right? And Colombia certainly wouldn't sell off identically named domains to companies looking to catch the typos of Canadians...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  8. Network Solutions == policy corruption by erlkonig · · Score: 4, Informative

    I've been on the Internet a long time, so I remember sri-nic.arpa, nic.ddn.mil, rs.internic.net, and even downloading the Internet host address file, with about 8000+ IPs in it. The early organization was very clear about preserving the namespace of domain names for future generations, with base policies (I believe these are all correct, but it might just be 3 out of 4) of:

    * The domain name must relate to the purpose of your organization.

    * .net is reserved for network infrastructure, .org for only non-profits, .com for commercial (.mil and .edu are still fairly pristine), etc.

    * You must establish two nameservers, that must not be on the same subnet, and must already be providing DNS for the requested domain.

    * Each requester gets a single domain, the idea being that the requester's entire organization would then be fully served.

    Although they weren't really thinking about the upcoming explosion in web use, their thinking certainly allowed for an explosion in *sub* domain names. So instead of lots of ridiculous domains like www.iatemygrandmamovie.com, we might have later seen something like iatemygrandma.movie.com, with some group running a movie.com site, and an easy way to find a bunch of them, instead of the crapshoot we have now.

    So where did the corruption set in? Once the idea of charging for a domain name popped up, some bright boy got a gleam in his eye when a company - I think it might have been Proctor and Gamble - violated registration policy by requesting scores of domain names based on ailments (and possibly some body parts). There was a similar polydomain request by some other group around the same time. Both generated a flurry of controversy. And our illustrious registrar suddenly demonstrated its modern, capitalist colors, dumping the past, conservative policies and making its new mission one of simply selling off every possible domain name, in every possible TLD, as fast as possible.

    Effectively, they sold out on future generations' needs in an exercise of total, corrupt greed. The registrar flipped on every policy, encouraging multiple registration of domains, flagrantly pushing registration in every possible TLD, dropping the domain server requirement, dropping the relevancy concept, and now even pushing for more TLDs, in order to sell even more completely unnecessary extra domains.

    The idea of allowing some company to register thousands of obviously unrelated domains for cybersquatting would have been anathema in the pre-profit days, but Network Solutions just doesn't care. And that ridiculous article completely misses *all* of this.