• Once your computer has the IP address, it sends a request to the server hosting that website.
• This request typically travels through multiple routers and servers across the internet to reach the destination server.

3.Web Hosting Server:

• The website you’re trying to visit is hosted on a server. This server stores the website’s files, such as HTML, CSS, images, etc.
• When your request reaches the server, it retrieves the necessary files to display the website in your browser.

4.Content Delivery Network (CDN) (Optional but common):

• Large websites often use CDNs to deliver content faster by storing copies of their website’s files on servers around the world.
• When you request a webpage, the CDN finds the closest server to you with a copy of that page and serves it, reducing load times.

5.Displaying the Website:

• Once the necessary files are retrieved, your browser assembles them to display the website’s content, including text, images, videos, etc.
• Any interactions you make on the website (clicking links, submitting forms, etc.) trigger additional requests and responses between your browser and the server.

That’s the basic process of how the internet finds and displays websites. It involves a series of steps, from translating domain names into IP addresses to retrieving and displaying the website’s content in your browser.

Process of DNS in detail:

1. Suppose we search for google.com, first, the OS will try to find the IP address of google.com in its own cache memory. If it can’t find the IP address it will send the query to the next level i.e., resolver server. The Resolver server is basically your ISP or Internet service provider
2. When the resolver receives the query it will check its own cache memory for the IP Address, if found it will send the IP address back to us. If the resolver can’t find the IP Address in its cache it will send a query to the next level i.e., Root server. There are 13 sets of root servers all across the world.
3. When the root server receives the query, the root server doesn’t know the IP address, but it knows where to send the resolver server to help find the IP Address. So the root server will direct the resolver to the TLD (Top Level Domain).
4. Now the resolver will ask the TLD for the IP address of google.com. TLD stores the address information for a top-level domain. Such as .com, .net, .org.
5. So, when the TLD receives the query for the IP Address of google.com. If the TLD doesn’t know the IP Address of google.com. It will redirect the resolver to the final level which is the Authoritative Name server.
6. Now the resolver will ask the authoritative name server for the IP address of google.com.
7. The Authoritative Name server is responsible for knowing everything about the domains. Which includes IP address. The Authoritative Name server will respond with the IP Address of google.com.
8. And finally, the resolver will tell us the IP address of google.com. And now our computer can retrieve the Yahoo web page.
9. The resolver will now store the IP address of google.com in its cache memory. So, if it receives another query for google.com it can directly reply back the IP Address. And it won’t have to go through all the steps again.

Caching for Efficiency:

• • • To avoid repetitive queries, browsers and ISPs often cache DNS results, making subsequent visits faster by retrieving information from the cache.

Conclusion:

Understanding DNS is akin to navigating a vast contact list for the internet. Just as we don’t memorize phone numbers, DNS efficiently maps domain names to IP addresses, ensuring seamless web accessibility. Browsers and ISPs play their roles by caching DNS results, making your online experience smoother. If you found this explanation helpful, let us know in the comments, and stay tuned for more simplified insights into fundamental concepts. Don’t forget to like and subscribe for more content!