Today I will start our AWS DNS service series, Amazon Route 53 . Route 53 is a DNS service for both AWS resources and your on-premise infrastructure. In Route 53 series, first I will configure a hosted zone and records sets. Then I will show how to configure health checks and configuring failover scenairos with route 53 like active-active, active-passive.
Let’s start our demonstration.
First I will create a hosted zone for my wekanban.com. On Route 53 dashboard, I click “Create Hosted Zone” and create my “wekanban.com” domain.
We can now create our records for our domain. Route 53 supports different types of records. Refer to this link to view the supported record types. There is an important record type which is “Alias”. Alias is a Route 53 specific record type and is used as a pointer for:
- S3 with a static website
- Other Route 53 record set
I will create two different records for my website. First one is an A record and will be for my “test.wekanban.com” website. The other one will be an Alias and I will point it to my ELB and serve my production website “www.wekanban.com”.
I’ve created 3 instances for my website.
For test.wekanban.com I will create an A record and use 184.108.40.206 value.
For www.wekanban.com I will create an Alias record and use my ELB as target.
As you see there are other options like routing policy and evaluate target health. I will explain them later.
It is time to test our records now.
If you will migrate your DNS server to AWS Route 53, you can use “import zone file” option. There are some limitations to use this option, like, the hosted zone must be empty and Route 53 ignores the SOA and NS records in the zone file.
Let’s import our sample zone file.
That was the fundamentals of Route 53. In my next post I will explain AWS Route 53 routing policies and health checks.
If you have any question or comment please feel free to write and don’t forget to share please.