HAA DNS Alternative

How to setup DNS for HAA?

The cluster name will be a prefix of an existing zone in DNS.  For example, if the existing zone is example.com, the cluster name would be redislabscluster.example.com .


The steps to create the DNS setting, are as follows:

1)    Create the delegation

a)    Right-click on the higher-level zone (example.com), and create a New Delegation.

b)    In the New Delegation Wizard, the Delegated Domain Name would be redislabscluster (in this example).

c)    Add a new Name Server with Add…

d)    In the Server FQDN field, enter the IP address of node1 and click Resolve.  This is OK for now; but a change is required later.

2)    Create the IP address records for the nodes in the cluster in the higher-level zone

a)    Right-click on the higher-level zone (example.com), and select New Host (A or AAAA)...

b)    Name field would be node1.redislabscluster in this example (note: not fully qualified).  Also enter the IP address for node1.  Each node will be defined by the node number and IP that appear in the Redis Labs “rladmin status” command line utility.  

c)    Repeat for node2 and node3, creating their A records as well.

3)    Configure the NS record

a)    Click on the delegated zone, and right-click on the Name Server record to get its properties.

b)    Click Edit… and type the FQDN for node1 in the Server FQDN field, node1.redislabscluster.example.com (in this example).

c)    Click Resolve, then click OK, then click Apply.  If prompted to delete the old glue record (the one with the IP address only), click Yes.

d)    Now repeat the process for node2 and node3 by clicking Add… and adding the FQDN for node2 and node3 in the Name Server Record.

4)    Refresh the zone

a)    Note for Win 2008 DNS Manager: The A records may disappear from the DNS Manager GUI once you Refresh the zone. In case troubleshooting is required, check C:\Windows\System32\dns\<name_of_forward_lookup_zone> to verify that the A-records and NS records exist.

It may take a few minutes, but once the DNS change is propagated, it should be possible to ping each node and the newly created database by FQDN.