To run mappings from an on-premises deployment of Big Data Management to a cluster on AWS, you must install and configure Unbound on an EC2 instance. Unbound enables DNS resolution from an on-premises network. To read how to install and configure Unbound in the AWS VPC, see the AWS documentation.

To run mappings from an on-premises deployment of Big Data Management to a cluster on Azure, you must use the Bind utility on the Azure virtural network.

Follow the steps in the Microsoft Azure article "DNS Configuration."

The article gives an example of the contents of the

/etc/bind/named.conf.options

file. You can put a list of available IP addresses on the domain network in the goodclients portion of the file. The following excerpt shows an example:

//Add the IP range of the joined network to this list
acl goodclients {
    1.2.3.0/24; # IP address range of the virtual network
    1.2.4.0/24;
    1.2.5.0/24;
    1.2.6.0/24;
    1.2.3.253;
    1.2.3.254;
    localhost;
    localnets;
};