Configuring DNS Nodes

This configuration is part of the configuration of the virtual machines in your Azure cloud infrastructure, which you will use for subsequent CloudBlue Commerce cloud deployment.

Before registering DNS nodes as slaves in CloudBlue Commerce

To be able to register DNS hosts (lindns01 and lindns02) in CloudBlue Commerce as slave nodes with PowerDNS, add to each DNS node and configure a dummy IP interface:

1. Go to one of the DNS nodes as a privileged user.

2. Remove the existing dummy module from the kernel to avoid glitches:

   # modprobe -r dummy

3. Add a new dummy module to the kernel:

   # modprobe -a dummy

4. Create a dummy ethernet interface. You can use any unused eth* name. For example, eth10 or eth7. In the example below, it is eth35:

   # ip link add eth35 type dummy

5. Find the public static IP address of the host in Azure Cloud as described in the official Azure documentation.

6. Assign the public static IP address that you found above to the created dummy ethernet interface (eth35, in our example):

   # ip address add <found_public_static_ip_address>/32 dev eth35

7. Repeat the procedure for the other DNS node.

After registering DNS nodes as slaves in CloudBlue Commerce

After registering the DNS hosts (lindns01 and lindns02) in CloudBlue Commerce as slave nodes with PowerDNS, remove the dummy IP interface from each DNS node:

1. Go to one of the DNS nodes as a privileged user.

2. Remove the dummy IP interface from the DNS node:

   # ip link del eth35

   where eth35 is the name of the previously created dummy ethernet interface.

3. Repeat the procedure for the other DNS node.