Configuring DNS for the Cluster Domain

This section describes the DNS requirements for deploying the Apcera Platform Enterprise Edition.

Configuring DNS is a chicken and egg situation. You need to have a registered domain name that you set in the cluster.conf file. But, you need to point the DNS server to the IP address of the HTTP router, which you won't know until you deploy the cluster. See configuring the cluster domain for details on where to set the domain name in the cluster.conf file.

DNS is required for cluster deployments

You need to configure DNS to point to the cluster.

DNS setup is not contingent on the cluster being up. All of the public IP allocations are done by the infrastrucutre provider configuration tool (such as Terraform), not by Orchestrator. You can configure DNS before, concurrent with, or after the Orchestrator deploy. The recommended approach is to populate the DNS at the same time as populating the cluster configuration, when setting the domain-name.

Apcera does not integrate directly with DNS and does not run any DNS servers to be delegated to. Often times, domain administrators will want to maintain ownership and control, so we simply rely on a few DNS records being created for the cluster.

It is only necessary for two DNS records to be created: {DOMAIN} and *.{DOMAIN}. These should be registered with DNS and pointing to the IP addresses of the HTTP routers, or the load balancer that fronts the routers.

If you are using TCP routing services (for non HTTP/HTTPS application communication from outside the cluster), you will also want to add tcp-services.{DOMAIN} (for example For AWS, you get the IP address from the Outputs > TCPRouter tab for the CloudFormation stack.

Configuring DNS

To configure DNS for an Apcera EE deployment:

  • Create an an “A” record” for the $base_domain entry to point to the HTTP routers (or load balancer if using).
  • Create a “CNAME” to *.$base_domain to point to the http routers (or load balancer if using).

AWS Route 53 DNS

If you are using the Route 53 DNS service from Amazon, complete the following steps and AWS will automatically route traffic to the Elastic Load Balancer (ELB) instance, which was configured by the CloudFormation template.

  • Go to the Route 53 dashboard
  • Create a Hosted Zone
  • Create a new DNS record set
  • Leave as is the Name (empty) and Type (IPv4)
  • Select the Alias > Yes option
  • Expand the Alias Target dropdown menu
  • Select your Elastic Load Balancer, which is populated by default. You can also get this from value from the Outputs tab > Elastic LB in the CloudFormation stack, or from the host name of the ELB instance.

Refer to the following screenshot for details on the DNS records you need:


Microsoft DNS

If you are using Azure, you may want to consider Microsoft DNS.