DNS Zones Delegation Requirements

DNS Zones Delegation Requirements

The platform must be able to manage the DNS zones assigned to it so that application addresses and internal platform resources can be created automatically.

For example, when the zone user.hosterdomain.com is delegated to the platform and an application named web-01 is created, the platform can automatically make it available at web-01.user.hosterdomain.com. Two platform DNS resolvers are deployed on the IP addresses defined in the deployment master plan.

On this page

Configuring DNS Zones Delegation

Two domain names must be delegated to the platform resolvers, which run on the Shared Load Balancers:

  • <infra-domain>.hosterdomain.com for platform infrastructure resources such as the administration panel and user dashboard.
  • <user-domain>.hosterdomain.com for end-user environments and their automatically generated hostnames.
Example: You may use infra.hosterdomain.com for infrastructure and user.hosterdomain.com for customer environments.

1. Add NS Records in the Parent Zone

<infra-domain>.hosterdomain.com. IN NS ns1.<infra-domain>.hosterdomain.com.
<infra-domain>.hosterdomain.com. IN NS ns2.<infra-domain>.hosterdomain.com.
<user-domain>.hosterdomain.com. IN NS ns1.<user-domain>.hosterdomain.com.
<user-domain>.hosterdomain.com. IN NS ns2.<user-domain>.hosterdomain.com.

2. Add Glue Records

ns1.<infra-domain>.hosterdomain.com. IN A 1.1.1.1
ns2.<infra-domain>.hosterdomain.com. IN A 2.2.2.2
ns1.<user-domain>.hosterdomain.com. IN A 1.1.1.1
ns2.<user-domain>.hosterdomain.com. IN A 2.2.2.2

Replace the sample addresses with the public IP addresses of the first and second platform resolvers.

Verifying Delegation

Use the following commands to check the infrastructure and user zones:

domain='<infra-domain>.hosterdomain.com'; tmp=${domain#*.}; for tmp in $(dig +short -t ns $tmp); do dig +norecurse -t soa @$tmp $domain; done | grep -vE '^(;|$)'

domain='<user-domain>.hosterdomain.com'; tmp=${domain#*.}; for tmp in $(dig +short -t ns $tmp); do dig +norecurse -t soa @$tmp $domain; done | grep -vE '^(;|$)'

When the delegation is correct, the result should contain NS records and, when applicable, A-type glue records.

user.example.com. 60 IN NS ns1.user.hosterdomain.com.
user.example.com. 60 IN NS ns2.user.hosterdomain.com.
ns1.user.hosterdomain.com. 60 IN A 1.1.1.1
ns2.user.hosterdomain.com. 60 IN A 2.2.2.2
Important: Do not create SOA records for the delegated infrastructure and user subdomains in the parent DNS zone. Their presence can prevent delegation from working correctly.

DNS Zones Delegation Use Case

The following example shows how to delegate infra.hosterdomain.com and user.hosterdomain.com using GoDaddy. The same principle applies to other domain registrars.

  1. Sign in to GoDaddy, open the domain manager, and select the parent domain.
  2. Open the DNS Zone File area and choose Add Record.
  3. Create the first NS record for the infrastructure domain and point it to ns1.infra.hosterdomain.com.
First NS record
Creating the first NS record
  1. Create the second NS record and point it to ns2.infra.hosterdomain.com.
Second NS record
Creating the second NS record
  1. Add an A record for ns1.infra.hosterdomain.com and assign the first resolver IP address.
First glue record
Creating the first A-type glue record
  1. Add an A record for ns2.infra.hosterdomain.com and assign the second resolver IP address.
Second glue record
Creating the second A-type glue record

Repeat the same NS and glue-record procedure for user.hosterdomain.com. After both zones are configured, the platform domains are delegated to the platform resolvers.

What’s next?

  • Hardware Requirements
  • Hardware Requirements Local Storage
  • Hardware Requirements Cloud Storage
  • Access Requirements