Overview of DNS Zones

introduction to dns zones

Prerequisite(s)

• Configure at least one Cloud Access of type "DNS Provisioning": Wayfinder needs to be given access to the cloud account, subscription or project where you wish your DNS zone to be created.

Why use DNS Zones in Wayfinder?

Configuring DNS Zones in Wayfinder allows for dynamic and automated delegation of child DNS zones from a parent DNS zone. This process is handled in a provider-agnostic way, ensuring consistent DNS management across different environments.

Do I Need Control of the FQDN?

You must have control over the top-level domain (TLD). For example, if you specify 'devapps.mycompany.com' as the Fully Qualified Domain Name (FQDN), you must own the 'mycompany.com' domain.

After the configuration in Wayfinder, you will need to update the parent domain (e.g., 'mycompany.com') with the name servers provided during this process. Each domain registrar has specific tools for modifying name server records. Once updated, return to Wayfinder, where it will check the delegation and notify you if it's correctly configured. Remember to allow enough time for DNS changes to propagate before returning to verify.

Child DNS Zones for Applications and Packages

Wayfinder automatically creates and manages child DNS zones for both applications and cluster-level packages within the specified workspace(s) and stage.

Examples:

• Application: Wayfinder generates mycoolapp.devapps.mycompany.com, where

  • mycoolapp is the application name,
  • devapps.mycompany.com is the FQDN, and
  • mycompany.com is the TLD.

• Packages: Wayfinder generates ws1-coolcluster.qa.mycompany.com, where

  • ws1 is the workspace,
  • coolcluster is the cluster name,
  • qa.mycompany.com is the FQDN, and
  • mycompany.com is the TLD.

What comes next?

• Get an overview on how to create a DNS Zone

Related Reading

• View existing DNS Zones