For Deis clusters on Amazon Web Services, Azure, DigitalOcean, Google Compute Engine, Linode, OpenStack, or bare metal, DNS records must be created. The cluster runs multiple routers infront of the Deis controller and apps you deploy, so a load balancer is recommended.
For local Vagrant clusters, no DNS configuration is required. The domain
local3.deisapp.com already resolves to the IPs of the first 3 VMs provisioned
by Deis’ Vagrantfile: 172.17.8.100, 172.17.8.101, 172.17.8.102.
deis.local3.deisapp.com to log in to the controller on a 3-node Vagrant
cluster. Apps that you deploy will have their name prefixed to the domain, such
local5.deisapp.com for a 5-node Vagrant cluster.
Deis requires a wildcard DNS record. Assuming
myapps.com is the top-level domain
apps will live under:
*.myapps.comshould have “A” record entries for each of the load balancer’s IP addresses
Apps can then be accessed by browsers at
appname.myapps.com, and the controller will be available to the Deis client at
These records are necessary for all deployments of Deis other than Vagrant clusters.
An alternative to configuring your own DNS records is to use xip to reference the IP of your load balancer. For example:
$ deis register http://deis.10.21.12.2.xip.io
You would then create the cluster with
10.21.12.2.xip.io as the cluster domain.
Note that xip does not seem to work for AWS ELBs - you will have to use an actual DNS record.