Custom Domain

By default, your service is reachable via a subdomain we provide. For example, node-6abceca0da1a7e72e26f1f86.de-north-2.xaas.plus.cloud. You also have the option to make your service additionally available under your own domain (Custom Domain).

To issue a valid SSL certificate for your service, we need access to the corresponding DNS records. There are two ways to set this up.

Option 1: Domain is hosted in PlusServer DNS

  • Our nameservers must be authoritative for your desired domain. You can check this with a whois lookup. The nameservers shown should be nsX.plusserver.com.
  • The domain must be registered under your customer account with us.

If you ordered your domain through PlusServer, this requirement is already met. Contact our support team if you need help assigning and delegating your domain accordingly.

Option 2: External domain

If an external nameserver is responsible for your desired domain, you need to create two DNS records in your DNS zone.

1. CNAME record to prove domain ownership

This record is required so that we can automatically issue a valid SSL certificate (Let’s Encrypt) for your domain.

FieldValueExample
TypeCNAMECNAME
Host_acme-challenge.<your-domain>_acme-challenge.idm.mydomain.de
Valuevp9z4fxvd3vvheqcwp7ebnarh5b3mah9q5rw9gqycg6wcu2hhbmpn2kak8h5zb4.verify.plusserver.com

2. A record pointing to your service

This record ensures that requests to your domain are actually routed to your service.

FieldValueExample
TypeAA
Host<your-domain>idm.mydomain.de
Valuethe external IP address of your service203.0.113.42

Note: Both records must be in place before the Custom Domain can be activated for your service.

Important: Do not change or remove the DNS records

As long as your service is in production use, the two DNS records mentioned above must not be changed or removed. Otherwise, the automatic renewal of your SSL certificate may fail, which would make your service unreachable under the Custom Domain.

Last modified 16.10.2026: remove dbaas couchdb (0ed68a86)