{
  "id": "configuring-aws-route53-dns-redis-enterprise",
  "title": "AWS Route53 DNS management",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/networking/configuring-aws-route53-dns-redis-enterprise/",
  "summary": "How to configure AWS Route 53 DNS",
  "content": "\nRedis Enterprise Software uses DNS to achieve high availability and fail-over regardless of where it is installed.\n\n\n## What is AWS Route 53?\n\nRoute 53 is a scalable DNS service by Amazon Web Service (AWS). It routes user traffic to AWS resources and external sites, offering DNS health checks, traffic management, and failover capabilities. It's integral for high-availability architectures and also provides domain registration services.\n\n## Create a hosted zone\n\nCreating a hosted zone in Amazon Route 53 is a foundational step in managing your domain's DNS settings.\n\nA hosted zone functions as a container for the DNS records of a specific domain. To create one, you first need to:\n\n1. Log into the AWS Management Console\n2. Navigate to the Route 53 dashboard\n3. Select \"Create Hosted Zone\"\n4. Enter your domain name, and choose public hosted zone\n\nThe hosted zone provides you with a set of Name Server (NS) records, which you will need to update at your domain registrar. This process effectively delegates the DNS management of your domain to Route 53, allowing you to create, update, and manage DNS records for your domain within the AWS ecosystem.\n\n\n\nOnce created, it will appear in the list of **Hosted zones**\n\n\n\n## Create glue records\n\nA **glue record** is a type of DNS record that helps prevent circular dependencies by providing the IP addresses of your nameservers. To create glue records in Route 53, you first need to set up a hosted zone for your domain. You will create a separate A record for each node in your Redis Enterprise cluster. The **Record name** will be a subdomain definition of the NS record you will define and the **value** should be set to the IP address of the node in your cluster.\n\n\n\nOnce complete, it should look something like this\n\n\n\n\n## Create nameserver record\n\nWhen you create a new hosted zone in Route 53 for your domain, a set of NS records is automatically generated. These records list the nameservers assigned by Route 53 to your domain.\n\nYou will need to create a new NS record which will point to the glue records created in the previous step.\n\n\nIt is important to make sure that the **Record Name** of the NS record equals the FQDN (Fully Qualified Domain Name) of your Redis Enterprise cluster. If not, DNS resolution will not function correctly.\n\n\n\n\n\n## Validate\n\nOnce all steps are completed, the configuration should look similar to this\n\n\n\nYou can test and validate your settings by using the ```dig``` command.\n\n```sh\ndig ns test.demo-rlec.redislabs.com\n\n; \u003c\u003c\u003e\u003e DiG 9.9.5-9+deb8u9-Debian \u003c\u003c\u003e\u003e ns test.demo-rlec.redislabs.com\n;; global options: +cmd\n;; Got answer:\n;; -\u003e\u003eHEADER\u003c\u003c- opcode: QUERY, status: NOERROR, id: 25061\n;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version: 0, flags:; udp: 4096\n;; QUESTION SECTION:\n;test.demo-rlec.redislabs.com. IN NS\n\n;; ANSWER SECTION:\ntest.demo-rlec.redislabs.com. 3409 IN NS node2.test.demo-rlec.redislabs.com.\ntest.demo-rlec.redislabs.com. 3409 IN NS node1.test.demo-rlec.redislabs.com.\ntest.demo-rlec.redislabs.com. 3409 IN NS node3.test.demo-rlec.redislabs.com.\n\n;; Query time: 31 msec\n;; SERVER: 192.168.1.254#53(192.168.1.254)\n;; WHEN: Tue Feb 14 16:49:13 CET 2017\n;; MSG SIZE  rcvd: 120\n```\n\nYou can see that the name are given a prefix of `ns-`. This answer does not come\nfrom *Route53* but from the cluster nameservers themselves.\n\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00"
}