DNS Hostnames for Direct Connection to Containers at Jelastic PaaS

By | May 10, 2018

Being able to easily connect to your Cloud services is a criteria of great importance for all of the developers. In Jelastic, each newly created node is assigned a number of automatically generated hostnames, pointed to the appropriate server internal/external IP address.   dns hostname aliases for docker containersDepending on a type of the created node, the set of hostnames for it could differ. With this article, you’ll learn all the possible ways to refer to a particular node, hosted at Jelastic PaaS, from both inside (i.e. when managing it via Jelastic SSH Gate) and outside of the Cloud. In addition, we’ll provide some useful hints on how to interconnect your nodes via Platform internal network.

So, let’s start with the most common hostnames, which are assigned to any container. And after that, we ’ll overview specific hostname aliases for Docker containers and dockerized Jelastic-managed stacks.

Hostnames for Specific Container

The following formats of node hostnames can be used in order to get internal IP of a specific container for the further access:

  • node${nodeId}${envName}.${platformDomain}
  • node${nodeId}.${envName}.${platformDomain}

Herewith, the highlighted placeholders should be replaced with the next values:

  • ${nodeId} – an automatically generated unique digit identifier, assigned to each container within a Platform      dns internal ip address
  • ${envName} – environment name (not an alias), specified during its creation
  • ${platformDomain} – domain name of a hosting service provider Jelastic installation

Both variants can be used for referring to the nodes from inside or outside of the platform (i.e. allowing to establish both internal and external connections).

Some of Jelastic certified stacks are provisioned with additional hostname prefixes (i.e. where the appropriate stack name is used instead of the node string) to make their management more convenient.

Hostnames for Specific Layers

For the new environments, you can get all internal IP addresses of containers within one node layer using the following hostname:

  • ${nodeGroup}.${envName}.${platformDomain}

where ${nodeGroup} placeholder is a name of a particular layer the required container belongs to. By default, layers are named in accordance with the appropriate nodeGroup specific role.

Note: Node groups added via the extra layers in the topology wizard are named in the same way, but with the appropriate ${N} index. Herewith, the default layers in topology wizard (e.g. bl, cp, sqldb, etc.) are considered as the first index, so the enumeration in extra layers starts with the second one, e.g. cp2, cp3, cp4, … (except of the extra, extra2, extra3, …). For example:

hostnames for layers

For example, this command can be used to get an application servers list for any environment within the platform:

application servers list

Tip: In order to get a list of containers for the current environment, just a short hostname can be used.

Herewith, every time a new container is created (removed) in a system, the appropriate record is automatically added to (removed from) DNS for the layer hostname.

Short Hostnames for Containers within One Environment

All the newly created Docker containers and dockerized Jelastic-managed stacks are provisioned with a specific DNS rule, which allows usage of the additional simplified hostname type:

  • node${nodeId} – alias to refer to a container in confines of a single environment

Utilizing such short domains in server configuration files, application source code and SSH console (within often used commands like ping, host, dig, etc) make operating with Dockerized stacks via Platform internal network much more convenient. Additionally, such approach enables painless environment migration to another hardware region through eliminating the necessity to adjust your application code due to the changed server location.

Hostnames for Linked Containers

Upon linking two environment layers, a set of dedicated DNS records are automatically added to the global Jelastic database. This allows to refer to the nodes within a target layer from the source ones (but not vice versa) when working in confines of these two layers using the following hostname aliases:

  • ${linkAlias} – to connect to a random node within target layer; an exact node to respond is chosen by means of the Round-Robin algorithm to ensure even load distribution
  • ${linkAlias}_${N} – to access a particular container within a target layer

Here, the appropriate placeholders are to be substituted with:

  • ${linkAlias} – link name you’ve specified during its setting (e.g. tomcat in the image below)    dns hostnames for linked containers
  • ${N} – nominal index number (in a 1…N range) of a particular container within the target linking layer (e.g. tomcat_1, tomcat_2), etc; herewith, master container is always considered the 1st instance, whilst the rest of nodes within a layer are assigned numbers according to their nodeID values, sorted in the ascending order (starting with the _2 index respectively)

For example, let’s suppose there are three containers on a layer – with the 123, 124 (master) and 125 IDs. According to the above-described implementation, the aliases will be assigned as follows:

  • alias_1 – link to the 124 container as a master node
  • alias_2 – will point to the 123 instance since it has the lowest ID among the remaining containers
  • alias_3 – for referring to the 125 container as the one with the next lowest nodeID

Note: By appending the environment domain to the alias ${linkAlias}.${envName}.${platformDomain}, the corresponding linked layer name can be resolved and accessed externally, i.e. from anywhere over the Internet. And by ${linkAlias}_${N} corresponding container of a linked layer can be resolved internally only, within the linked layers network.

Now, you know all the specifics and shortcuts that can be used to refer to your nodes, which will help to quickly and efficiently organize connections between your application instances. Try this and a lot of other features of Jelastic PaaS for yourself with a free two-week trial on one of our numerous hosting partners around the world.

Subscribe to get the latest updates