Skip to main content

Custom Domain

Support
  • Updated

By default, the DPS application is reachable to the subdomain of *.servitly.com, for instance acme.servitly.com, but in addition you can use your own domain (e.g. under the OEM public domain), for instance:

  • cooking-as-a-service.cloud
  • www.cooking-as-a-service.cloud
  • bake365.acme.com

Configuring a custom domain

To configure a custom domain, you must:

  1. Purchase a domain name from your domain registrar.
  2. Configure your DNS according to the DNS Records Configuration paragraph.
  3. Within the Servitly Console, enter the Access and Security / Domain page.
  4. Add the domain aliases, for instance bake365.acme.com.
    You will be able to register multiple domain aliases for the same DPS portal.
    A domain alias can be registered to only one DPS portal at a time.
  5. Configure the SSL Certificate Management required to access the application securely (HTTPS).
  6. Save and wait for DNS propagation, if needed.

 

You must provide the SSL certificate associated with the registered domain aliases. The Console will validate that the provided certificate is not expired and matches the added domain aliases.

The provided SSL files must be in the *.pem format. 

Remember to register the right records in your DNS management page.

Let's Encrypt is a certificate authority that offers free SSL certificates that you can use for your custom domain name. By using Let's Encrypt, certificate are automatically generated and renewed by the DPS application through the ACME protocol of Let's Encrypt.
Remember to register the right records in your DNS management page.

External Proxy

You must configure and keep updated and external proxy, for instance an Apache Virtual Host.

Here is an example of an Apache Virtual Host configuration that you can use as a starting point for your own.

<VirtualHost *:443>
   ServerName DOMAIN_ALIAS
   <Location "/ws">
     ProxyPass ws://ENVIRONMENT_DOMAIN/ws/
     Header add Connection Upgrade
     RequestHeader add Connection Upgrade
     Header add Upgrade websocket
     RequestHeader add Upgrade websocket
   </Location>
   ProxyPass / https://ENVIRONMENT_DOMAIN/ retry=1
   ProxyPassReverse / https://ENVIRONMENT_DOMAIN/
   SSLEngine on
   SSLProxyEngine On
   SSLCertificateFile "/etc/ssl/certs/customerCertificate.crt"
   SSLCertificateKeyFile "/etc/ssl/certs/customerCertificate.key"
</VirtualHost>

Where placeholders are:

  • DOMAIN_ALIAS: your custom domain alias (e.g. devices.acme.com).
  • ENVIRONMENT_DOMAIN: the Servitly domain where the environment is reachable (e.g. acme.servitly.com) 

Remember to register the right records in your DNS management page.

DNS Records Configuration

According to the type of registered domain, you must add different records to your DNS:

  • Second-level (e.g. cooking-as-a-service.cloud)
    An A record should be added and pointed to the DPS server public IPs.
    For the list of public IP addresses, you can refer to the Architecture Overview page.
  • Third-level (e.g. www.cooking-as-a-service.cloud)
    A CNAME record should be added and mapped to the default public domain (acme.servitly.com).

Note that www.cooking-as-a-service.cloud is a third-level domain and therefore different from cooking-as-a-service.cloud.

When updating a CNAME, pay attention to the presence of a cache time out.
Any changes to DNS may take some time before they become public.

From the command line, it is possible to check whether the pointing was performed correctly

// Linux
dig cooking-as-a-service.cloud

// Windows
nslookup cooking-as-a-service.cloud

 

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.