RapidAPI Comic on DNS
RapidAPI Comic How DNS works cover.
DNS stands for domain name system. DNS is the system that translates domain names into IP addresses. Computers and servers use IP addresses to identify websites and direct your browser to the correct one.
An internet address book full of IP addresses. You can think of the DNS system acting this way.
The first step of DNS is cache. When you enter a domain and click search, your browser checks to see if the website is already stored in its cache. The DNS system stops here if it is cached, and the site is loaded in your browser. If it's not cached, the DNS system continues.
The second step of the DNS system is the Resolver server. Your internet service provider(ISP) typically manages Resolvers. A searched domain is sent to a Resolver server. If the Resolver does not have the site in its cache, it passes it to the next level of servers.
Step three is the Root server. Root servers are at the top of the DNS hierarchy. Their job is to send your request to the appropriate TLD server (Top Level Domain). If we search for RapidAPI.com, our request is sent to the .com TLD server.
Step four is the TLD server. There are TLD servers for domain endings such as .com, .net, .org, etc. There are also TLD servers for country codes such as .in for India or .de for Germany. TLD servers will not find the IP address, but they will send the request to the final level of servers.
The final step is the Authoritative Name Server. These servers are responsible for knowing everything about domains and delivering the correct IP address to the Resolver server.
The Resolver Server delivers the IP address back to the client browser, and the website is loaded. This entire system may take only a few milliseconds. That's the end of the DNS system.