6

Sounds like a dumb question but I bet a lot of people don't know either. I understand servers, clients, modems, routers, ISP's, ect; but what I don't understand is what makes up the backbone structure of the internet. I have never seen any clear UML diagram or description of the backbone of the internet. I have heard things about 7 main servers (don't quote me on that), but who owns each server, when were they built, how old are they, how do they interact? It seems surprisingly hard to find information on this.

All my google searching provides seemingly vague and outdated information.

Edit: Sorry if you found this question vague, not only did I write it late last night, but I have a vague understanding of how the backbone of the net works thus making my question vague.

  • Gee, thank goodness this isn't an excessively huge and vague question... – womble Jul 11 '09 at 11:34
  • Seriously, while it's understandable for people to ask questions like this, this really isn't the venue. – Cian Jul 11 '09 at 19:34
  • I cant ask a question about the internet on SERVER Fault? – PostulatedAxiom Jul 11 '09 at 23:30
  • No, it's not suitable for Server Fault. How does a question such as this relate to system administration? The connection is as tenuous as asking about basic electrical theory. – John Gardeniers Jul 11 '09 at 23:37
  • 5
    Let's play nice, and the question will either get answered or get downvoted to close. Opinions will always vary. :) – Kara Marfia Jul 11 '09 at 23:41
  • @John Gardeniers I would think someone who is a system admin would have to have a detailed understanding of the internet to do their job. – PostulatedAxiom Jul 12 '09 at 00:02
  • @teh_noob: I agree. However, this isn't a venue for anyone to ask questions of systems administrators. It's a venue for those of us who *are* systems administrators to ask other systems administrators questions about systems administration. This is not that – Cian Jul 12 '09 at 00:15
  • I am a system administrator, sort of lol, I run a server out of my room. – PostulatedAxiom Jul 12 '09 at 02:14
  • @Kara Couldn't agree more. I suspect some of the people downvoting here never bothered to read the post and just decided the title alone wasn't sophisticated enough for them. I wonder if the question would be downvoted if the title had been "wan topology 101" – username Jul 12 '09 at 02:38

6 Answers6

24

I'll take a stab at this:

First thing first, no one owns or controls the internet. Right now there is defacto control provided through the DNS servers, which are what change "www.google.com" into "IP address 123.456.789.000". These DNS "root" servers control the domain name infrastructure that provides the web as many people know it.

However the internet is actually a network of networks controlled by people (hence inter - network). If you imagine that you have a network of computers controlled by a cable provider, by a telephone provider, network them to a government network, network them to a link to europe, another to hawaii, another to asia, another to Australia, you can see how the internet starts to take shape. Essentially companies and in some cases countries will pay to have their internet connected to a link in a network to america. Once these links were established the internet really started to take shape.

From a hardware point of view, the internet is built upon IP (not TCP/IP). IP was a system that provides for networking using a shared address space (the familiar www.xxx.yyy.zzz) addressing system with a notion of a "gateway" which is if I don't know the person who owns this packet I'll forward it to someone who does. Essentially there was a routing network created which defines which routers control certain IP ranges. That way if I can digress, for your computer to send a packet in america to a computer in australia, the following would happen.

  1. You send the packet via your modem to your ISP.
  2. Your ISP uses it's rules to determine it doesn't own the IP of the packet and forwards it to it's backbone or a Tier 1 provider.
  3. The backbone will determine that this packet is for australia and sends it to a machine connected to a fibre link or possibly over a satellite etc.
  4. This process happens in reverse from the backbone, to the ISP, to the local ISP connection, to the modem in the house, to the computer in the house.

Now when you realise that the routing rules have redundancy (ie. you have more than one route to send a packet to australia for instance, picking a different cable, or using a sattelite) you can start to understand how the internet can survive when computers or routers shut down or fail, which is a key part of the infrastructure.

So if you have a network that can get packets to anyone who is connected, and anyone can connect by agreement to tier 1 connections, you can combine the capability to talk to any computer on the network with a protocol to send information, such as HTTP, FTP, SSL etc. you end up with the internet as it exists.

A final word: If you managed to soak all of that in, you can see now that the argument between "well everyone should be able to watch youtube and make VOIP calls without it EVER being throttled" doesn't mesh so well with the fact that the people who are providing the internet have to share it with networks which they don't control. I'm speaking about net neutrality of course.

Spence
  • 670
  • 3
  • 9
  • 19
11

It's really a series of tubes.

hayalci
  • 3,611
  • 3
  • 25
  • 37
  • 5
    Not a truck...? – RainyRat Jul 11 '09 at 12:04
  • @RainyRat: that's the high bandwidth version :-p – hayalci Jul 11 '09 at 12:47
  • 3
    I'm gonna get laughed at for this, but the "series of tubes" analogy isn't really all that bad. The book "The Victorian Internet" (http://tomstandage.wordpress.com/books/the-victorian-internet/) describes the communication networks, composed of pneumatic tubes, telegraphs, bicycle messengers, and postal mail, of the 19th century. (You could send a message "by tube" to a telegraph office, which would send the message on to another city where it could be picked-up by a bicycle messenger and delivered to the recipient in a few minutes.) It's a rocking book, and I highly recommend it. – Evan Anderson Jul 11 '09 at 15:25
  • @Evan: "A series of tubes" is not, in fact, a bad analogy to settle the questions of the un-geeky. But it is a horrible analogy to rely on when trying to make policy about how to run or regulate the internet. Really, mind-bogglingly bad. Which is why the Senator is rightly laughed at and derided. – dmckee --- ex-moderator kitten Jul 11 '09 at 15:47
  • @dmckee: I laughed at Sen. Stephens because I think he literally believed it was a series of tubes. – Evan Anderson Jul 11 '09 at 15:53
  • Hmmm... a bit more explanation would have deserved my vote up for this answer, even though I know what you mean and agree. – l0c0b0x Jul 12 '09 at 04:36
4

I guess you're talking about root servers. These one are used for DNS, without them you would not be able to connect to computers using a name.
Your question is a bit complex to answer because the term Internet is a large things. If we only consider IP level, Internet is just a lot of routers interconnected together.

radius
  • 9,545
  • 23
  • 45
4

The backbone of the internet is composed of loooong strands of optical fiber, which interconnect different datacenters (IXP - Internet eXchange Points), where different ISPs keep their routers, make peerings (interconnections).

So, "who owns the internet?" - well - ISPs, who buy the routers, switches (usually from Cisco), ask other firms to make new connections (via optical fiber) to other PoPs (Points of Presence) or other ISPs (peerings) and implement new protocols (IPv6, multicast transmissions).

Some interesting links:

http://en.wikipedia.org/wiki/Internet_exchange_point

http://en.wikipedia.org/wiki/List_of_Internet_exchange_points_by_size

Later edit: You may also want to read about the BGP - the main routing protocol for the "core" of the internet - http://en.wikipedia.org/wiki/BGP

adrians
  • 333
  • 2
  • 6
-1

in a word cisco - lol.

in reality it works simply on lot of pipes connection oodles of computers all mostly passing on anonymous bits of data till it get's (usually) to the right place. Some are big computers some are small some pipes are wide and fast others are slow. But in essence its all just one logical forwarding system. A bit like a really fast postal system.

Preet Sangha
  • 2,727
  • 1
  • 24
  • 25
-2

Pigeons. We'd be lost without the little guys running the packets around. See RFC 1149 and RFC 2549 for more information.

theotherreceive
  • 8,235
  • 1
  • 30
  • 44