github.com/rvaralda/deis@v1.4.1/docs/managing_deis/configure-dns.rst (about)

     1  :title: Configure DNS
     2  :description: Configure name resolution for your Deis Cluster
     3  
     4  .. _configure-dns:
     5  
     6  Configure DNS
     7  =============
     8  
     9  For Vagrant clusters, we've created the DNS record ``local.deisapp.com`` which resolves to the IP of the first VM, 172.17.8.100.
    10  You can use ``local.deisapp.com`` to both log into the controller and to access applications that you've deployed (they will be subdomains of ``local.deisapp.com``, like ``happy-unicorn.local.deisapp.com``). Similarly, you can use ``local3.deisapp.com`` or ``local5.deisapp.com`` for 3- and 5-node clusters, respectively. No DNS configuration is necessary for Vagrant clusters.
    11  
    12  For Deis clusters hosted elsewhere (EC2, Rackspace, DigitalOcean, Google Compute Engine, bare metal, etc.), DNS records will need to be created to point to the cluster. For a one-node cluster, we schedule and launch one router, and deis-router and deis-controller will run on the same host. So, the DNS record specified below can be configured to point to this one machine.
    13  
    14  On a multi-node cluster, however, there are probably multiple routers, and the controller will likely be scheduled on a separate machine. As mentioned in :ref:`configure-load-balancers`, a load balancer is recommended in this scenario.
    15  
    16  Note that the controller will eventually live behind the routers so that all external traffic will flow through the load balancer - configuring a DNS record which points to a service whose IP could change is less than ideal.
    17  
    18  .. _dns_records:
    19  
    20  Necessary DNS records
    21  ---------------------
    22  
    23  Deis requires a wildcard DNS record. Assuming ``myapps.com`` is the top-level domain apps will live under:
    24  
    25  * ``*.myapps.com`` should have "A" record entries for each of the load balancer IP addresses
    26  
    27  Apps can then be accessed by browsers at ``appname.myapps.com``, and the controller will be available to the Deis client at ``deis.myapps.com``.
    28  
    29  `EC2 recommends`_ against creating "A" record entries; instead, create a wildcard "CNAME" record entry for the load balancer's DNS name, or use Amazon `Route 53`_.
    30  
    31  These records are necessary for all deployments of Deis (EC2, Rackspace, DigitalOcean, Google Compute Engine, bare metal, etc.). Vagrant clusters can use the domain ``local.deisapp.com``, ``local3.deisapp.com``, or ``local5.deiaspp.com``.
    32  
    33  .. _xip_io:
    34  
    35  Using xip.io
    36  ------------
    37  An alternative to configuring your own DNS records is to use `xip`_ to reference the IP of your load balancer. For example:
    38  
    39  .. code-block:: console
    40  
    41      $ deis register http://deis.10.21.12.2.xip.io
    42  
    43  You would then create the cluster with ``10.21.12.2.xip.io`` as the cluster domain.
    44  
    45  Note that xip does not seem to work for EC2 ELBs - you will have to use an actual DNS record.
    46  
    47  .. _`EC2 recommends`: https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html
    48  .. _`Route 53`: http://aws.amazon.com/route53/
    49  .. _`xip`: http://xip.io/