DNS stands for Domain Name System.
DNS is used when you use an internet. DNS is used to convert human-friendly domain names into an Internet Protocol (IP) address.
IP addresses are used by computers to identify each other on the network.
IP addresses are of two types, i.e., Ipv4 and Ipv6.
Domains are seperated by a string of characters seperated by dots. For example, google.com, gmail.com, etc.
The last word in a domain name is known as a Top Level Domain.
The second word in a domain name is known as a second level domain name.
.com: .com is a top-level domain.
.edu: .edu is a top-level domain.
.gov: .gov is a top-level domain.
.co.uk: .uk is a top-level domain name while .co is a second level domain name.
.gov.uk: .uk is a top-level domain name while .gov is a second level domain name.
The Top level domain names are controlled by IANA (Internet Assigned Numbers Authority).
IANA is a root zone database of all available top-level domains.
You can view the database by visiting the site: http://www.iana.org/domains/root/db
Domain Registrar is an authority that assigns the domain names directly under one or more top-level domains.
Domain Registrar is used because all the names in a domain name must be unique there needs to be a way to organize these domain names so that they do not get duplicated.
Domain names are registered with interNIC, a service of ICANN, which enforces uniqueness of domain name across the internet.
Each domain name is registered in a central database known as the WhoIS database.
The popular domain registrars include GoDaddy.com, 123-reg.co.uk, etc.
SOA stores the information in Domain Name System (zone) about the zone and other DNS records. Where DNS zone is a space allocated for a particular type of server.
Each DNS zone consists of a single SOA record.
The name of the server that supplies the data for the zone.
The administrator of the zone, i.e., who is administering the zone.
The current version of the data file that contains the zone.
The default number of records for the time-to-live file on resource records. For example, when you are dealing with a DNS, then it always has a time-to-live. Time-to-live must be lower as possible because when you make changes, it then propagates quicker. Suppose the name of the website is Hindi100.com and its time-to-live is 60 seconds. By the end, you want to change its IP address then the time taken to achieve this is equal to the time-to-live.
The number of seconds a secondary name server has to wait before checking for the updates.
The maximum number of seconds that a secondary name server can use the data before it is either be refreshed or expire.
NS stands for Name Server records.
NS Records are used by Top Level Domain Servers to direct traffic to the Content DNS server which contains the authoritative DNS records.
Suppose the user wants an IP address of hindi100.com. If ISP does not know the IP address of hindi100.com, ISP goes to the .com and asks for the NS Record. It finds that time-to-live is 172800 and its ns record is ns.awsdns.com. ISP moves to this ns record and asks that "do you know hindi100.com". Yes, it knows, so it points to Route53. In SOA, we have all the DNS types and 'A' records.
An 'A' record is a fundamental type of DNS record.
'A' stands for Address.
An 'A' record is used by the computer to convert the domain name into an IP address. For example, https://www.javatpoint.com might point to http://123.10.10.80.
The length that a DNS record is cached on either the Resolving power or the users owns local PC is equal to the value of the TTL in seconds.
The lower the time-to-live, the faster changes to DNS records take to propagate throughout the internet.
A CNAME can be used to resolve one domain name to another. For example, you may have a mobile website with a domain name http://m.devices.com which is used when users browse to your domain name on their mobile devices. You may also want the name http://mobile.devices.com to resolve the same address.
Alias Records are used to map resource record sets in your hosted zone to Elastic load balancers, CloudFront distributions, or S3 buckets that are configured as websites.
Alias records work like a CNAME record in that you can map one DNS name (http://www.example.com) to another target DNS name (elb1234.elb.amazonaws.com).
The key difference between a CNAME and Alias Record is that a CNAME cannot be used for naked domain names (zone apex) record, i.e., it cannot be used when something is written infront of the domain name. For example, http://www.example.com contains a www infront of the domain name, therefore, it cannot be used for CNAME.
Route 53 is a web service that is a highly available and scalable Domain Name System (DNS.)
Let’s understand what is Amazon Route 53 in technical terms. AWS Route 53 lets developers and organizations route end users to their web applications in a very reliable and cost-effective manner. It is a Domain Name System (DNS) that translates domain names into IP addresses to direct traffic to your website. In simple terms, it converts World Wide Web addresses like www.example.com to IP addresses like 10.20.30.40.
Basically, domain queries are automatically routed to the nearest DNS server to provide the quickest response possible. If you use a web hosting company like GoDaddy, it takes 30 minutes to 24 hours to remap a domain to a different IP, but by using Route 53 in AWS it takes only a few minutes.
Interested in learning AWS from experts? Check out AWS Training Course now!
AWS Route 53 connects requests to the infrastructure running in AWS. These requests include AWS ELB, Amazon EC2 instances, or Amazon S3 buckets. In addition to this, AWS Route 53 is also used to route users to infrastructure outside of AWS.
AWS Route 53 can be easily used to configure DNS health checks, continuously monitor your applications’ ability to recover from failures, and control application recovery with Route 53 Application Recovery Controller. Further, AWS Route 53 traffic flow helps to manage traffic globally via a wide variety of routing types including latency-based routing, geo DNS, weighted round-robin, and geo proximity. All these routing types can be easily combined with DNS Failover in order to enable a variety of low-latency, fault-tolerant architectures.
Let us understand, step by step, how does AWS Route 53 work:
A user accesses www.example.com, an address managed by Route 53, which leads to a machine on AWS.
The request for www.example.com is routed to the user’s DNS resolver, typically managed by the ISP or local network, and is forwarded to a DNS root server.
The DNS resolver forwards the request to the TLD name servers for “.com” domains.
The resolver obtains the authoritative name server for the domain—these will be four Amazon Route 53 name servers that host the domain’s DNS zone.
The DNS resolver chooses one of the four Route 53 servers and requests details for the hostname www.example.com.
The Route 53 name server looks in the DNS zone for www.example.com, gets the IP address and other relevant information, and returns it to the DNS resolver.
The DNS resolver returns the IP address to the user’s web browser. The DNS resolver also caches the IP address locally as specified by the Time to Live (TTL) parameter.
The browser contacts the webserver or other Amazon-hosted services by using the IP address provided by the resolver.
The website is displayed on the user’s web browser.
Now, take a look at the benefits provided by Route 53.
Route 53 provides the user with several benefits.
They are:
Highly Available and Reliable
Flexible
Simple
Fast
Cost-effective
Designed to Integrate with Other AWS Services
Secure
Scalable
Highly Available and Reliable
AWS Route 53 is built using AWS’s highly available and reliable infrastructure. DNS servers are distributed across many availability zones, which helps in routing end users to your website consistently.
Amazon Route 53 Traffic Flow service helps improve reliability with easy re-route configuration when the system fails.
Flexible
Route 53 Traffic Flow provides users flexibility in choosing traffic policies based on multiple criteria, such as endpoint health, geographic location, and latency.
Simple
Your DNS queries are answered by Route 53 in AWS within minutes of your setup, and it is a self-service sign-up.
Also, you can use the simple AWS Route 53 API and embed it in your web application too.
Distributed Route 53 DNS servers around the world make a low-latency service. Because they route users to the nearest DNS server available.
Cost-effective
You only pay for what you use, for example, the hosted zones managing your domains, the number of queries that are answered per domain, etc.
Also, optional features like traffic policies and health checks are available at a very low cost.
Designed to Integrate with Other AWS Services
Route 53 works very well with other services like Amazon EC2 and Amazon S3.
For example, you can use Route 53 to map your domain names or IP addresses to your EC2 instances and Amazon S3 buckets.
Secure
You can create and grant unique credentials and permissions to each and every user with your AWS account, while you have to mention who has access to which parts of the service.
Scalable
Amazon Route 53 is designed to automatically scale up or down when the query volume size varies.
These are the benefits that Amazon Route 53 provides, moving on with this what is Amazon Route 53 tutorial, let’s discuss the AWS routing policies.
Amazon Route 53 is a robust DNS service with advanced features, but it has several limitations as well. Some of them are discussed below:
No DNSSEC support: DNSSEC stands for Domain Name System Security Extensions. It is a suite of extensions specifications by the Internet Engineering Task Force. It is used to secure the data exchanged in DNS in Internet Protocol networks. It is not supported by AWS Route 53.
Forwarding options: Route 53 does not provide forwarding or conditional forwarding options for domains used on an on-premise network.
Single point of failure: Used in conjunction with other AWS services, Route 53 may become a single point of failure. This becomes a major problem for AWS route 53 disaster recovery and other relevant issues.
Limited Route 53 DNS load balancing: The features of AWS Route 53 load balancer lack advanced policy support and enterprise-class features and provide only basic load balancing capabilities.
Route 53 Cost: For businesses using Route 53 with non-AWS endpoints or services, the service is expensive. In particular, the visual editor is costly including the cost of each query.
No support for private zone transfers: AWS Route 53 DNS cannot be appointed as the authoritative source for cloud websites.com, even after having the root-level domain registered.
Latency: All AWS Route 53 queries must be forwarded to external servers after contacting Amazon infrastructure.
When buying a solution, buyers often compare and evaluate similar products by different market players based on certain parameters such as specific product capabilities, integration, contracting, ease of deployment, and offered support and services. Based on the mentioned parameters and a few more, we have listed some potential AWS Route 53 alternatives below:
Azure DNS: It allows you to host your DNS domain in Azure. This helps to manage DNS records by using the same credentials, billing, and support contract just as other Azure services.
Cloudflare DNS: As a potential alternative to AWS Route 53, Cloudflare DNS is described as the fastest, privacy-first consumer DNS service. It is a free-of-charge service for ordinary people; however, professionals and enterprises have to take up a monthly subscription.
Google Cloud DNS: Google Cloud DNS is a scalable, reliable, and managed authoritative DNS service that runs on the same infrastructure as Google.
DNSMadeEasy: It offers affordable DNS management services that are easy to manage. It also has the highest uptime and amazing ROI.
DNSimple: With DNSimple, you can register a domain quickly with no upselling and hassles.
Avi Vantage is a next-generation, full-featured elastic application of azure services fabric that offers a range of application services such as security, monitoring and analytics, load balancing, and multi-cloud traffic management for workloads. All workloads are deployed in bare metal, virtualized, or container environments in a data center of a public cloud such as AWS. Avi Vantage delivers full-featured load balancing capabilities in an as-a-service experience and easily integrated Web Application Firewall (WAF) capabilities.
Enterprises often leverage the power of AWS in order to maximize and modernize infrastructure utilization. The next phase of this modernization is represented by extending app-centricity to the networking stack.
Avi Networks integrates with AWS Route 53 and delivers elastic application services that extend beyond load balancing to deliver real-time app and security insights, simplify troubleshooting, enable developer self-service, and automation.
The user merges a private center with one of their Amazon VPCs using a managed VPN or AWS Direct Connect in a typical hybrid cloud environment. As the private cloud and the user’s VPC is a pre-established connection to AWS, whenever a lookup is performed across this connection, it often fails. As a result, some users reroute requests using on-premises DNS servers to another Amazon VPC server. It can perform outbound communication from VPC to the data center and inbound communication from an on-premises source to VPC.
Some of the advantages of AWS Route 53 resolver are as follows:
Security: AWS benefits from the added security of Identity Access Management (IAM). AWS IAM allows secure user control access to all web resources and services. It can also assign specific permissions to allow or deny access to AWS resources and the creation and management of AWS users or groups.
Cost: AWS Route 53 proves to be really cost-effective as it redirects website requests without extra hardware and does not charge for queries to CloudFront distributions, ELBs, S3 buckets, VPC endpoints, and other AWS resources.
Reliability: All features of Route 53, such as geographically-based and latency-based policies, are designed to be highly reliable and cost-effective. In addition to this, Amazon Route 53 is designed to help the system stay running in a coordinated way with all the other AWS services.
There are several types of routing policies. The below list provides the routing policies which are used by AWS Route 53.
Simple Routing
Latency-based Routing
Geolocation Routing
Simple Routing
Simple routing responds to DNS queries based only on the values in AWS route table. Use the simple routing policy when you have a single resource that performs a given function for your domain.
Latency-based Routing
If an application is hosted on EC2 instances in multiple regions, user latency can be reduced by serving requests from the region where network latency is the lowest. Create a latency resource record set for the Amazon EC2 resource in each region that hosts the application. Latency will sometimes change when there are changes in the routes.
Interested in learning AWS? Go through this AWS Tutorial!
Geolocation Routing
Geolocation routing can be used to send traffic to resources based on the geographical location of users, e.g., all queries from Europe can be routed to the IP address 10.20.30.40. Geolocation works by mapping IP addresses, irrespective of regions, to locations.
Now, you understood that Route 53 in AWS maps the end user to an IP address or a domain name. But, where are the routes stored?
An AWS route table contains a set of rules or routes, which is used to determine where the network traffic is directed to.
All subnets in your VPC have to be attached to an AWS route table, and the table will take control of routing for those particular subnets. A subnet cannot be associated with multiple route tables at the same time, but multiple subnets can be connected with a single AWS route table. An AWS route table consists of the destination IP address and the target.
These are the benefits provided by Route 53. What key features make Route 53 special?
Traffic Flow
You can route end users to the best endpoint possible according to your application’s geo proximity, latency, health, and other considerations.
Latency-based Routing
You can route end users to the AWS region with the lowest possible latency.
Geo DNS
You can route your end users to the endpoint which is present in their specific region or the nearest geographic location.
DNS Failover
You can route your end users to an alternate location to avoid website crashes or outages.
Health Checks and Monitoring
The Health and performance of your website or application is monitored by Amazon Route 53. Your servers can be monitored as well.
Domain Registration
You can search for and register available domain names using Amazon Route 53. A full list of currently available Top-level Domains (TLDs) are provided with the current pricing.
Step 1: Log in to the AWS Management Console Step 2: Click on Route 53 in the Services drop-down
Now, go to www.freenom.com or any website for which you want to get a domain name. Freenom is completely free; for a demo, just use a domain from freenom.
Step 3: Go to Route 53 dashboard and click on Create Hosted Zone
Step 4: Provide the domain you have created in the domain field and keep the website as a public hosted site
Step 5: Now, you will have a nameserver (NS) and Start of Authority (SOA) type recordsets. Copy the content of the nameserver value textbox and paste it in the Custom nameservers of your domain name
After pasting nameservers, click on Change Nameservers.Remove the dots at the end of your nameserver values in both places
Step 6: Create two recordsets with the type ‘A’ and leave one as the same. For the other, add ‘www’ so that both domain names redirect to the EC2 instance IP address you have provided. If you want to know how to create an EC2 instance, check out the AWS EC2 blog and do as per the hands-on steps mentioned there.
Step 7: After completing all these steps perfectly, type the domain name in your browser’s URL tab. As you can see, the website is now online and available publicly on the Internet
You have successfully hosted your first website!
In this what is amazon route 53 in AWS, we have discussed the concepts of Route 53, how it works, what are AWS route tables and the key features provided by Amazon Route 53. Keep visiting for more tutorials on Services offered by AWS.
