How does web hosting really work?

Every time we visit a website or download a file from the internet, a hidden set of events needs to occur correctly. Have you ever wondered how it all works?

The Digital Address Book (DNS)
Let’s use Ulatu as an example. We already know the domain name (ulatu.com). However, to connect to the server, we need an IP address. A good analogy is your phone’s contact list. You know your friend’s name, but you probably dont remember their number. You need to use a number to make a call, so your phone converts that name to the friend’s number when you hit “call”

Your web browser needs to determine the correct IP address using DNS. Generally, when you type a web address into your browser, it will first query your ISP’s DNS servers. This will result in an IP address being returned.

DNS example: Ulatu.com >> DNS Lookup >> 206.72.206.46

But how does your ISP know what IP address is associated with your domain name? This information is actually published by your web hosting account as part of the local DNS. The DNS that resides within your account forwards details to central registries. This data is then replicated to different DNS servers worldwide as it propagates. This is why it can sometimes take up to 48 hours for new DNS settings to take effect—you are waiting for the world’s address books to update.

The Handshake (The Connection)
Your browser now has the web address and the correct IP address. It can now connect to the server that resides at that IP address. This connection is carried out over TCP/IP (Transmission Control Protocol / Internet Protocol).

You can think of this as a digital handshake. However, this step is where the magic of shared hosting begins. The browser connects to the IP and announces the domain name it is looking for (using the HTTP ‘Host’ header). The server listens to this announcement to figure out exactly which website you want.

Multiple Sites on a Single Server (Virtual Hosting)
Within a web hosting environment, it is common practice to have many websites share the same physical hardware. It is also extremely common to have them share the same IP address. You may think this will cause confusion. If a browser is trying to access a site hosted on an IP address, how does it return the correct website and not another site that shares that IP address?

Remember our previous analogy about an address book? Well, the same process occurs in reverse. Because the browser announced the domain name during the handshake, the server knows exactly which website you are looking for. The server checks its internal configuration, finds the correct location on the file system (for example, /home/ulatu/public_html), and gathers the requested files.

Unpacking the Delivery (Rendering)
The server doesn’t just send a blank page, it sends back a package containing HTML (the structure), CSS (the design and colours), and JavaScript (the interactive elements). Your browser receives this package, reads the code line-by-line, and paints the pixels on your screen. This final step is why you see a designed homepage rather than a jumble of code.

The Takeaway
From the moment you hit ‘Enter’ to the moment the page appears, a complex chain of DNS lookups, TCP handshakes, server configurations, and file rendering occurs in mere milliseconds.