Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What happen when you type in www.google.com #README #2300

Open
marwasabon opened this issue May 27, 2024 · 2 comments
Open

What happen when you type in www.google.com #README #2300

marwasabon opened this issue May 27, 2024 · 2 comments

Comments

@marwasabon
Copy link

DNS Infrastructure

@marwasabon
Copy link
Author

marwasabon commented May 27, 2024

The infrastructure of the Domain Name System (DNS) is a complex network of servers and protocols that enable the translation of human-readable domain names into IP addresses, allowing computers to communicate with each other on the internet. The DNS infrastructure consists of several key components and layers, including:

Root Servers: At the top of the DNS hierarchy are the root servers, which are responsible for maintaining a list of authoritative name servers for top-level domains (TLDs) like .com, .org, .net, etc. There are 13 root servers distributed globally, operated by various organizations.

TLD Name Servers: Below the root servers are the TLD name servers, which handle queries for specific TLDs. For example, the name servers for .com TLD are responsible for maintaining information about domain names ending in .com.

Authoritative Name Servers: Authoritative name servers are responsible for storing and serving DNS records for individual domain names. When a DNS query is made, the authoritative name server for the requested domain provides the IP address associated with that domain.

Recursive Resolvers: These are DNS servers provided by internet service providers (ISPs) or other organizations. When a user makes a DNS query, the recursive resolver acts as an intermediary between the user and the DNS infrastructure. It recursively queries other DNS servers until it obtains the final IP address for the requested domain.

@softontechsolution
Copy link

Wrote and published an article explaining how the client request is sent to the local DNS, from there to the DNS resolver, ETC to get the server IP address thereafter sending the server IP to the client.
I also considered a situation where a firewall is installed or some form of load balancing is on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants