Custom Domain Name

Custom Domain Name

A custom domain lets users access an application through a branded web address instead of the default environment URL. The configuration normally includes purchasing a domain, creating the correct DNS record and binding the domain to the environment when required.

Before configuring a custom domain, it is helpful to understand a few basic terms:

Domain

The complete address entered in a browser, including the top-level domain, second-level domain and any optional subdomain.

Root Domain

The second-level and top-level domain together, such as example.com.

DNS

The system that translates a readable domain name into the IP address used to locate the application.

In this article

Purchase a Domain

Purchase the required domain from a domain registrar. The exact interface differs between providers, but the process normally includes creating an account, selecting an available domain and completing the registration.

Domain registrar account
Open the domain registrar account and select the required domain.

Configure the DNS Record

After purchasing the domain, add a DNS record that points the custom domain to the application environment.

1

Open DNS management

Locate the required domain in the registrar account and open its Manage DNS or DNS settings page.

Manage DNS option
Open the DNS management page for the selected domain.
2

Add a new record

In the DNS records section, click Add or the equivalent option provided by the registrar.

Add DNS record button
Add a new DNS zone record.
3

Select the record type

Select the required DNS record type, such as A, CNAME or ANAME, according to the environment setup.

DNS record type selector
Select the DNS record type.
4

Complete the record details

For an A Record, configure the host, destination IP address and TTL value, then save the record.

HostEnter @ to point the root domain directly, or enter a subdomain such as www or app.
Points toEnter the public IP address of the environment entry point, application server or load balancer.
TTLSelect how long DNS resolvers should cache the record before checking for an updated value.
✓

Finding the public IP

Expand the application server or load balancer node in the platform dashboard and copy the displayed public IP address.

Environment public IP address
Copy the public IP from the environment topology.
i

DNS propagation

DNS changes may require several hours to propagate worldwide. In some cases, complete propagation can take up to 48 hours.

Choose the Correct DNS Record

A RecordMaps a domain or subdomain to a public IP address. Use it when the environment has an attached public IP.
CNAMEMaps a custom subdomain to the default environment hostname. Additional domain binding is normally required in the platform dashboard.
ANAMEMaps a root domain to another hostname when the DNS provider supports ANAME or an equivalent ALIAS record.

A Record Example

app.example.com  →  111.111.111.111
www.example.com  →  111.111.111.112

CNAME Example

app.example.com  →  environment.provider-domain.com

ANAME Example

example.com  →  provider-domain.com
i

Production recommendation

For production environments, a public IP with an A Record is generally the most direct configuration. CNAME or ANAME can be used when traffic is routed through a shared load-balancing layer.

Bind the Domain to the Environment

Domain binding is required when the DNS record points to the environment hostname through CNAME or ANAME and the request is routed through the shared load balancer. Binding helps the platform route incoming traffic to the correct environment.

1

Open environment settings

Click the environment’s Settings button in the platform dashboard.

Environment settings button
Open the settings of the target environment.
2

Bind the custom domain

Open Custom Domains, enter the full domain name and click Bind.

Bind custom domain to environment
Enter the custom domain and bind it to the environment.
i

Public IP exception

Domain binding is generally unnecessary when the environment uses a public IP because requests bypass the shared load balancer.

Expected Result

After DNS propagation and any required domain binding are complete, the application becomes accessible through the configured custom domain. The default environment URL may continue to work unless separately restricted.

Important Notes

  • Use an A Record when the environment has a public IP.
  • Use CNAME for subdomains mapped to the environment hostname.
  • Use ANAME or ALIAS only when supported by the DNS provider.
  • Bind the domain in the platform when using CNAME or ANAME through shared load balancing.
  • Allow sufficient time for DNS propagation.
  • Configure SSL after the domain begins resolving correctly.

What’s next?