Setting Up DNS on AWS Route 53

This article provides step-by-step guidance for Setting Up DNS on AWS Route 53 to support Redis clusters. It covers key steps such as Creating Hosted Zones, Delegating Subdomains, and Configuring NS and A Records for Redis nodes. You’ll also find a Troubleshooting Table for common DNS issues, along with Additional Resources to support successful configuration and validation of your Route 53 setup.

Prerequisites

• An AWS account with permissions to manage Route 53.

• A registered domain (e.g., example.com), either through AWS or an external registrar.

• Access to the AWS Management Console.

• Publicly accessible IPs (Elastic IPs) for all Redis cluster nodes.

Step-by-Step Instructions

1. Create a Hosted Zone

• Sign in to the AWS Management Console.

• Navigate to Route 53 > Hosted zones.

• Click Create hosted zone.

• Enter your domain or subdomain (e.g., demo-rlec.redislabs.com).

• Choose Public hosted zone.

• Click Create hosted zone.

2. Note the AWS Name Servers

• After creating the zone, Route 53 generates a set of NS records.

• Copy these NS values—you will need them to delegate the subdomain at your registrar (if applicable).

3. Create a Delegated Subdomain for Redis Cluster

• For example: fl.demo-rlec.redislabs.com

• In the Route 53 hosted zone, click Create record.

• Create an NS record:

  • Name: redis-cluster

  • Type: NS

  • Values:

    

  • Click Create records.

4. Create A Records for Each Node

• Still in the same zone (b12.lab), create one A record per Redis node:

  • Example entries:

• In Route 53:

  • Click Create record for each node.

  • Name: node1.redis-cluster.b12.lab

  • Type: A

  • Value: Corresponding Elastic IP

  • Repeat for all nodes.
    
    

5. Update Name Servers at Your Registrar (if required)

• If you purchased your domain outside AWS:

  • Log in to your registrar’s control panel.

  • Navigate to DNS settings for demo-rlec.redislabs.com.

  • Replace the NS records with the Route 53-provided NS values.

  • Save and wait for propagation (can take 24–48 hours).

6. Verify DNS Propagation

• Use DNS tools like dig, nslookup, or DNS Checker to confirm setup:

   

  

Troubleshooting

DNS Changes Not Propagating

• Double-check that the NS records were replaced at the registrar.

• Allow up to 48 hours for changes to propagate.

• Use whois to confirm current NS records.

Incorrect Record Types

• Use A records for IP mapping, not CNAME, for Redis nodes.

• Ensure subdomain NS records are correctly typed and scoped.

Cluster Not Reachable by FQDN

• Confirm that Redis nodes' IPs match the A record values.

• Ensure UDP port 53 is open and not blocked by firewall rules.

Additional Resources

Configure Cluster DNS

AWS Route 53 Documentation

AWS Route 53 Console

Add or Replace Nodes in Redis

Manage Networks