Internet’s Navigator: Understanding DNS A.K.A Domain Name System

DNS aka Domain Name System, mainly interprets domain names (for instance, www.temok.com) to machine clear IP addresses (such as 192.036.2.14). All PCs on the Internet, from your advanced mobile phone or laptop to the servers that serve content for monstrous retail sites, discover and connect with each other by utilizing numbers. These numbers are known as IP addresses. At the point when you open an internet browser and go to a site, you don't need to recall and enter a long number. Rather, you can enter relevant domain name like temok.com and still end up to the desired website across the internet.

A DNS administration decodes domain name like www.temok.com into the numeric IPs such as 192.044.2.1 that PCs use to associate with one another. The Internet's DNS framework works a lot of like a telephone directory by dealing with the mapping among names and numbers. DNS servers make an interpretation of requests for names into IP addresses, controlling which server an end client will arrive at when they type a space name into their internet browser. These user requests are called queries.

Types of DNS Service

Authoritative DNS: An authoritative DNS administration gives a specific update mechanism that software engineers use to deal with their open DNS names. It at that point answers DNS inquiries, making an interpretation of domains into IPs so PCs can connect with one another. Authoritative DNS has the last authority over an area and is liable for furnishing answers to recursive DNS servers with the IP address data. 

Recursive DNS: Customers ordinarily don't make questions straightforwardly to the authoritative DNS administrations. Rather, they tend to interface with another sort of DNS administration known a resolver, or a recursive DNS administration. A recursive DNS administration acts like a lodging attendant: while it doesn't possess any DNS records, it goes about as a mediator who can get the DNS data for your benefit. On the off chance that a recursive DNS has the DNS reference reserved, or put away for a while, at that point it answers the DNS inquiry by giving the source or IP data. If not, it passes the inquiry to at least one definitive DNS servers to discover the data.

How Does DNS Route Traffic to Your Web Application?

Below I have stated a step-by-step guide how a DNS routes traffic to one’s application.

1. A client opens an internet browser, enters www.temok.com in the location bar, and presses Enter. 

2. The user request for www.temok.com is steered to a DNS resolver, which is ordinarily overseen by the client's Internet specialist organization (ISP, for example, a digital Internet supplier, a DSL broadband supplier, or a corporate system. 

3. The DNS resolver for the ISP advances the solicitation for www.temok.com to a DNS root name server. 

4. The DNS resolver for the ISP advances the solicitation for www.temok.com once more, this opportunity to one of the TLD name servers for .com areas. The name server for .com domain reacts to the solicitation with the names of the four name servers that are related with the temok.com domain. 

5. The DNS resolver for the ISP picks a name server and advances the solicitation for www.temok.com to that name server. 

6. The name server looks in the temok.com facilitated zone for the www.temok.com record, gets the related worth, for example, the IP address for a web server, 192.890.2.44, and restores the IP address to the DNS resolver. 

7. The DNS resolver for the ISP at long last has the IP address that the client needs. The resolver restores that incentive to the internet browser. The DNS resolver additionally reserves (stores) the IP address for example.com for a measure of time that you determine with the goal that it can react all the more rapidly whenever somebody peruses to example.com. For more data, see time to live (TTL). 

8. The internet browser sends a solicitation for www.temok.com to the IP address that it got from the DNS resolver. 

9. The web server or other asset at 192.970.2.44 returns the site page for www.temok.com to the internet browser, and the internet browser shows the page.

DNS Servers and IP Addresses

You recently have learned about the core purpose of a domain name server, or DNS server, is to determine (make an interpretation of) a domain name into an IP address. That seems like a straightforward errand, and it would be, with the exception of the accompanying focuses: 

? There are billions of IP being used, and most machines have a comprehensible name too. 

? DNS servers (aggregately) are handling billions of solicitations over the web at some random time. 

? Millions of individuals are including and changing domain names and IPs to every day. 

With such a great amount to deal with, DNS servers depend on organize effectiveness and web conventions. Some portion of the IP's viability is that each machine on a system has an extraordinary IP address in both the IPV4 and IPV6 measures oversaw by the Internet Assigned Numbers Authority (IANA).

The Big Picture

All in a nutshell, At the point when you question a domain name your initial step won't really be at the root name servers. Rather, your program will ask your local resolving name server in the event that they have any DNS records for that domain. 

The local resolving name server is normally your ISP (Internet Service Provider), and if it's a well-known site like youtube.com they will probably have the record in their reserve. For this situation, you would avoid the remainder of the DNS query process. 

Although, these records are saved for a brief timeframe. At whatever point you make a record; you have the alternative to set a TTL (Time to Live). TTL's tell settling name ser local resolving name server to what extent they can store the record data. TTL's can go somewhere in the range of 30 seconds to seven days. 

Imagine a scenario where the record we are searching for isn't stored. At that point the local resolving name server will approach the root name servers for the TLD for that area, which will direct you toward the supplier authoritative for facilitating the records.

For More Info: https://www.temok.com/blog/dns-infrastructure/