Skip to main content

Route 53: Why You Should Consider Migrating your DNS Needs to AWS

What AWS Route 53 brings to the DNS table

Amazon Route 53 is a highly available and scalable DNS service offered by AWS. Like any DNS service, Route 53 handles domain registration and routes users’ Internet requests to your application – whether it’s hosted on AWS or elsewhere.

But Route 53 also intelligently directs traffic based on sophisticated routing policies and, through automated health checks, away from servers that might be failing.

Like many AWS services, Route 53 is a pay-as-you-go service. You will be charged for the number of hosted zones you create and maintain and by the number of requests routed.

In my previous post, I discussed some of the basics of how DNS works.  Now we will explore the value that Route 53 can create for your domain needs and why and how you might want to migrate your domains over to Route 53.

Why you should consider migrating to Route 53
Once you’ve got your domain up and running, you can choose a routing policy that best fits your needs. To get the most out of the service however, you’ll need to properly understand the function of each policy type.

Simple Routing Policy

This is the most common and, as the name suggests, simplest routing type. If, say, your application server has a public IP address of 205.251.242.103, and you’d like to use the human readable address of amazon.com (assuming it’s available, of course), then you would use Route 53 to map amazon.com to your IP. From then on, any browser requests for amazon.com would be directed to 205.251.242.103.

Weighted Routing Policy

By assigning different numeric weights (or “priorities”) to multiple servers providing a web service, you can direct a higher or lower percentage of your incoming traffic to one particular server over another. This kind of routing can be useful for load balancing and testing new versions of a software package.

route 53

Latency based Routing Policy

A latency based policy directs traffic requests to the server that will be able to respond with the lowest possible latency (delay). You could, for instance, run your application in multiple AWS regions, and Route 53 will automatically route users to those that will deliver the quickest.

Route 53


Failover Routing Policy

A failover policy will send all traffic to the server you set as primary for as long as that server is still healthy. If, however, health checks determine that it’s failing, traffic will be diverted to a designated backup resource.

Route 53


Geolocation Routing Policy

This policy lets you designate resource targets based on your users’ geographic location. So, for example, you might want all queries from India to be routed to a server located in the same physical region in order to limit latency.

Some Route 53 features

Domain Registration. You can purchase domains from all top level domains (.com, .net, .org, etc.) directly from route 53, avoiding the need to migrate altogether. Route 53 also provides privacy protection for your WHOIS record at no extra charge.
Private DNS. Private DNS records let you create private hosted zones and route traffic using easily managed domain names within your VPCs. This can, for instance, allow you to quickly switch between IP-based resources without the need to update multiple embedded links.
Health Check. Route 53 monitors the health  of your application and, when an outage is detected, redirects users to a healthy resource.
AWS service integration. Route 53 is tightly integrated with Elastic Load Balancing (ELB), CloudFront, and S3. You can easily route traffic to an ELB CNAME record, a static website hosted on S3, or generate custom domains for your CloudFront URLs.
Alias Records. Instead of an IP address, an alias resource record can, for instance, point directly to a CloudFront distribution, ELB load balancer, or Amazon S3 bucket. This way, even if the IP addresses of the underlying resources should change, traffic will still be sent to the correct endpoint.

Migration options

  1. Leave your domain name with your own registrar

    If you would like to use Route 53’s routing features, but have no need to move your domain name from its current registrar, you simply need give your registrar the new name server addresses you’ll get from Route 53 upon creating a hosted zone. Once you have updated your name servers with your own providers, Route 53 will ensure the routing of all new domain requests through its own name servers.

  2. Migrate your domain name to Route 53

    When you decided to migrate, you will need get the DNS record data from your DNS provider. You will then import this data to a Route 53 hosted zone, and replace the registrar’s name server records with AWS name servers that you get by clicking on “GethostedZone”. Depending on your TTL settings, changes will take place within 24 to 48 hours.

For more insight into Amazon’s DNS service, take Cloud Academy’s Route 53 course.

Written by

My professional IT career began nine years back when I was just out of my college. I worked with a great team as an infrastructure management engineer, managing hundreds of enterprise application servers. I found my passion when I got the opportunity to work with Cloud technologies: I'm addicted to AWS Cloud Services, DevOps engineering, and all the cloud tools and technologies that make engineers' lives easier. Currently, I am working as a Solution Architect in SixNines IT. We are an experienced team of engineers that have helped hundreds of customers move to the cloud responsibly. I have achieved 5 AWS certifications, happily helping fellow engineers across the globe through my blogs and answering questions in various forums.

Related Posts

— November 28, 2018

Two New EC2 Instance Types Announced at AWS re:Invent 2018 – Monday Night Live

Let’s look at what benefits these two new EC2 instance types offer and how these two new instances could be of benefit to you. Both of the new instance types are built on the AWS Nitro System. The AWS Nitro System improves the performance of processing in virtualized environments by...

Read more
  • AWS
  • EC2
  • re:Invent 2018
— November 21, 2018

Google Cloud Certification: Preparation and Prerequisites

Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2018, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the first time. In t...

Read more
  • AWS
  • Azure
  • Google Cloud
Khash Nakhostin
— November 13, 2018

Understanding AWS VPC Egress Filtering Methods

Security in AWS is governed by a shared responsibility model where both vendor and subscriber have various operational responsibilities. AWS assumes responsibility for the underlying infrastructure, hardware, virtualization layer, facilities, and staff while the subscriber organization ...

Read more
  • Aviatrix
  • AWS
  • VPC
— November 10, 2018

S3 FTP: Build a Reliable and Inexpensive FTP Server Using Amazon’s S3

Is it possible to create an S3 FTP file backup/transfer solution, minimizing associated file storage and capacity planning administration headache?FTP (File Transfer Protocol) is a fast and convenient way to transfer large files over the Internet. You might, at some point, have conf...

Read more
  • Amazon S3
  • AWS
— October 18, 2018

Microservices Architecture: Advantages and Drawbacks

Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).Microservices have become increasingly popular over the past few years. The modular architectural style,...

Read more
  • AWS
  • Microservices
— October 2, 2018

What Are Best Practices for Tagging AWS Resources?

There are many use cases for tags, but what are the best practices for tagging AWS resources? In order for your organization to effectively manage resources (and your monthly AWS bill), you need to implement and adopt a thoughtful tagging strategy that makes sense for your business. The...

Read more
  • AWS
  • cost optimization
— September 26, 2018

How to Optimize Amazon S3 Performance

Amazon S3 is the most common storage options for many organizations, being object storage it is used for a wide variety of data types, from the smallest objects to huge datasets. All in all, Amazon S3 is a great service to store a wide scope of data types in a highly available and resil...

Read more
  • Amazon S3
  • AWS
— September 18, 2018

How to Optimize Cloud Costs with Spot Instances: New on Cloud Academy

One of the main promises of cloud computing is access to nearly endless capacity. However, it doesn’t come cheap. With the introduction of Spot Instances for Amazon Web Services’ Elastic Compute Cloud (AWS EC2) in 2009, spot instances have been a way for major cloud providers to sell sp...

Read more
  • AWS
  • Azure
  • Google Cloud
— August 23, 2018

What are the Benefits of Machine Learning in the Cloud?

A Comparison of Machine Learning Services on AWS, Azure, and Google CloudArtificial intelligence and machine learning are steadily making their way into enterprise applications in areas such as customer support, fraud detection, and business intelligence. There is every reason to beli...

Read more
  • AWS
  • Azure
  • Google Cloud
  • Machine Learning
— August 17, 2018

How to Use AWS CLI

The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services.So you’ve been using AWS for awhile and finally feel comfortable clicking your way through all the services....

Read more
  • AWS
Albert Qian
— August 9, 2018

AWS Summit Chicago: New AWS Features Announced

Thousands of cloud practitioners descended on Chicago’s McCormick Place West last week to hear the latest updates around Amazon Web Services (AWS). While a typical hot and humid summer made its presence known outside, attendees inside basked in the comfort of air conditioning to hone th...

Read more
  • AWS
  • AWS Summits
— August 8, 2018

From Monolith to Serverless – The Evolving Cloudscape of Compute

Containers can help fragment monoliths into logical, easier to use workloads. The AWS Summit New York was held on July 17 and Cloud Academy sponsored my trip to the event. As someone who covers enterprise cloud technologies and services, the recent Amazon Web Services event was an insig...

Read more
  • AWS
  • AWS Summits
  • Containers
  • DevOps
  • serverless