- When a Client logs onto the Internet, the ISP tells it what DNS to start with when looking up IP addresses for domain names on the web.
- Client device sends a request (e.g. webpages, images, videos,etc.) using HTTP or HTTPS
- TCP/IP breaks the request into packets of data.
- TCP/IP sends the packets wirelessly to Wi-Fi Router
- Wi-Fi Router sends the data packets through a coaxial/fiber optic cable that connects to your ISP network
- Routers in the ISP network sends your request packets from one ISP server to another until it reaches the destination server that has the content you requested.
- When the Client requests teamtreehouse.com, the DNS system begins by looking at the top level domain or .com in the case of teamtreehouse.com.
- It will then ask which server the domain teamtreehouse is on, if it doesn’t already know.
- Within DNS there’s a hierarchy of servers, so if one doesn’t know, it sends a request to the next server, and the next, until the correct location of the website is found.
- If all goes well, the server sends back a response to you also split into packets.
- The response usually is constituted of a short message saying that everything is okay (i.e. HTTP status code), followed by the web page or the content itself.
- The server’s response arrives to the client the same way.
- Data packets are reassembled.
- Depending on the response, the browser shows you the content.