Connecting to the internet: ISPs, DNS and everything in between

What this lesson covers

This lesson follows what happens when someone types google.com into a browser. The browser hands the request to the computer's network card, which connects to a router, usually one set up by an internet service provider. The router has no idea where Google's server is or what google.com means, so it asks a central server that holds a mapping of names to IP addresses, for example google.com to 1.1.1.3 and interviewready.io to 1.1.1.4. The mapping matters because a business can move to another machine or cloud provider and change the address while keeping its name. Registering a name with a company such as GoDaddy is compared to renting land. The servers holding the mapping are domain name servers (DNS), and with the other servers that work out where packets go, the internet backbone, they resolve a name by asking around until one of them knows. Once the router has the IP address, the packet goes from router to router, each hop saying where to go next, and the response comes back the same way to the home router's address, which the ISP advertises to the central services. The video ends on security: someone with physical access to a home router could point it at a private DNS and redirect requests to their own site, and a rogue router in the middle could do the same, though the backbone's operators work to keep random routers out.

  • The router does not know what google.com means and asks a domain name server, which maps the name to an IP address such as 1.1.1.3
  • The name to address mapping lets a business change servers or cloud providers without changing its name
  • Packets travel router to router, each hop saying where to go next, and the ISP advertises the home router's address
  • With physical access to a router an attacker can point it at a private DNS and redirect requests to their own site
  • The internet backbone's operators use agreements and secure setup to stop a random router joining in the middle