Home Full Form DNS Full Form: What Is DNS and About All Details

DNS Full Form: What Is DNS and About All Details

964
0

What exactly is DNS Full Form?

DNS Full Form: The Domain Name System (DNS) converts human-readable domain names (such as www.amazon.com) to machine-readable IP addresses.

DNS Fundamentals

All machines on the Internet use numbers to find and connect with one another, from your smartphone or laptop to the servers that deliver content for big retail websites.

The IP addresses are the names for these numbers. You don’t have to remember and input a long number when you open a web browser and go to a website. Instead, you can type in a domain name like example.com and be directed to the correct location.

A DNS Full Form (Domain Name System) and services such as Amazon Route 53, are a globally distributed service that converts human-readable names such as www.example.com into numeric IP addresses such as 192.0.2.1 that computers use to connect to one another.

The DNS system on the Internet manages the mapping between names and numbers in a similar way to a phone book. DNS servers convert requests for names into IP addresses, allowing users to choose which server they want to visit when they type a domain name into their browser. Queries are the term for these requests.

Different Types of DNS Services

Authoritative DNS: An authoritative DNS service is a service that allows developers to control their public DNS names by providing an updating method. It then responds to DNS requests by converting domain names to IP addresses, allowing computers to communicate with one another.

Authoritative DNS has final authority over a domain and is responsible for supplying IP address information to recursive DNS servers. Amazon Route 53 is a DNS scheme that is authoritative.

Clients rarely query authoritative DNS services directly, hence recursive DNS is used. Instead, they usually link to a resolver, also known as a recursive DNS service, which is a different type of DNS service. A recursive DNS service functions similarly to a hotel concierge.

it does not hold any DNS records, but it acts as an intermediary to obtain DNS information on your behalf. When a recursive DNS cache or stores a DNS reference for a length of time, it responds to a DNS query by providing the source or IP information. If you can’t find the information, it sends the query to one or more authoritative DNS servers.

What is DNS’s role in traffic routing to your web application?

The graphic below shows how authoritative and recursive DNS services work together to direct a user to your website or application.

1. A user launches a web browser and types www.example.com into the address box.

2. A DNS resolver, which is normally handled by the user’s Internet service provider (ISP), such as a cable Internet provider, a DSL broadband provider, or a corporate network, receives the request for www.example.com.

3. The ISP’s DNS resolver routes www.example.com requests to the DNS root name server.

4. The ISP’s DNS resolver sends the request for www.example.com to one of the TLD name servers for.com domains once more. The names of the four Amazon Route 53 name servers associated with the example.com domain are returned by the name server for.com domains.

5. The ISP’s DNS resolver selects an Amazon Route 53 name server and routes www.example.com requests to that server.

6. The Amazon Route 53 name server looks for the www.example.com record in the example.com hosted zone, retrieves the associated value, such as 192.0.2.44, and delivers the IP address to the DNS resolver.

7. The ISP’s DNS resolver now has the IP address that the user requires. The web browser receives that value from the resolver. DNS resolver also caches (stores) the IP address for example.com for the time period you selected, so it can respond faster the next time someone visits example.com. See Time to Live for further details (TTL).

8. The web browser requests www.example.com using the IP address obtained from the DNS resolver. This is where your content is stored, for example, on an Amazon EC2 web server or an Amazon S3 bucket configured as a website endpoint.

9. A web server or other resource at 192.0.2.44 sends www.example.com’s web page to a web browser, where the browser displays.

Also Read: