github.com/technosophos/deis@v1.7.1-0.20150915173815-f9005256004b/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 Deis clusters on Amazon Web Services, Azure, DigitalOcean, Google Compute Engine,
    10  Linode, OpenStack, or bare metal, :ref:`DNS records <dns_records>` must be created.
    11  The cluster runs multiple routers infront of the Deis controller and apps
    12  you deploy, so a :ref:`load balancer <configure-load-balancers>` is recommended.
    13  
    14  Vagrant
    15  -------
    16  
    17  For local Vagrant clusters, no DNS configuration is required. The domain
    18  ``local3.deisapp.com`` already resolves to the IPs of the first 3 VMs provisioned
    19  by Deis' Vagrantfile: 172.17.8.100, 172.17.8.101, 172.17.8.102.
    20  
    21  Use ``deis.local3.deisapp.com`` to log in to the controller on a 3-node Vagrant
    22  cluster. Apps that you deploy will have their name prefixed to the domain, such
    23  as "golden-chinbone.local3.deisapp.com".
    24  
    25  Similarly, use ``local5.deisapp.com`` for a 5-node Vagrant cluster.
    26  
    27  .. _dns_records:
    28  
    29  Necessary DNS records
    30  ---------------------
    31  
    32  Deis requires a wildcard DNS record. Assuming ``myapps.com`` is the top-level domain
    33  apps will live under:
    34  
    35  * ``*.myapps.com`` should have "A" record entries for each of the load balancer's IP addresses
    36  
    37  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``.
    38  
    39  `AWS 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`_.
    40  
    41  These records are necessary for all deployments of Deis other than Vagrant clusters.
    42  
    43  .. _xip_io:
    44  
    45  Using xip.io
    46  ------------
    47  An alternative to configuring your own DNS records is to use `xip`_ to reference the IP of your load balancer. For example:
    48  
    49  .. code-block:: console
    50  
    51      $ deis register http://deis.10.21.12.2.xip.io
    52  
    53  You would then create the cluster with ``10.21.12.2.xip.io`` as the cluster domain.
    54  
    55  Note that xip does not seem to work for AWS ELBs - you will have to use an actual DNS record.
    56  
    57  .. _`AWS recommends`: https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html
    58  .. _`Route 53`: http://aws.amazon.com/route53/
    59  .. _`xip`: http://xip.io/