CluedIn PaaS

Configure DNS

On this page

  1. DNS entries
  2. Update DNS configuration for CluedIn

As part of the CluedIn configuration, a base URL is used to make the application easily accessible by your browser. For proper configuration of CluedIn, you need to update the DNS settings. Specifically, you need to ensure that the A-records are configured to point either to your public IP address or a private IP address.

Important! Changing your DNS settings could have an impact on your TLS/SSL configuration. If you are also using specific TLS ingress hosts, they will also need to be changed to reflect your new DNS.

DNS entries

In this article, we’ll use deparmentX as an example of the organization name that was entered during the installation of CluedIn and as an example of the main domain.

You need to have the A-records for the following DNS entries:

At CluedIn, we use the following environments:

  • Development environment – for partners and developers to customize CluedIn.
  • Test environment – for business users to validate the work implemented by development teams (with non-production data).
  • Production environment – for business users to operate CluedIn using real-world data.

We recommend that you set up those environments (development, test, and production) using the name convention of your choice.

Example of DNS entries for the CluedIn environments

Update DNS configuration for CluedIn

After you add the needed DNS entries, update your DNS configuration for CluedIn.


  • You should be comfortable working in either PowerShell or bash terminal via Azure Cloud Shell.
  • You should be connected to your AKS cluster.

    See Connect to CluedIn cluster for detailed instructions.

  • Your Helm repository is set up.

If you have any questions about DNS configuration, you can request CluedIn support by sending an email to (or reach out to your delivery manager if you have a committed deal).

To update the DNS configuration for CluedIn

  1. Download the current cluster configuration file by running the following command:
    helm get values cluedin-platform -n cluedin -o yaml > Cluster-Current-values.yaml
  2. Open the file in a text editor of your choice
  3. In the file, find the block of code similar to what is shown below. Look for the entry named dns. It is the configuration that controls the DNS address used by CluedIn.
         # subdomains:
           # openrefine: cluedin-clean-dev
           # application: cluedin-app-dev
         # If you want to deviate away from the standard 'app' and 'clean' subdomains, you need to add the
         # `subdomains` block of code and ensure that they match in the global.ingress.tls.hosts section as well.

    Note: For environments sharing a second-level domain such as, it’s important to plan the domains in advance to avoid issues during the onboarding process.

  4. Edit the value of hostname to reflect your desired domain for the given environment.
  5. Find the TLS hosts section. The example of the section is shown below.

           - '*'
  6. Replace the hosts section as shown below.

           - '*'
  7. Save the file and apply changes from the local file to the CluedIn cluster by running the following command:
    helm upgrade -i cluedin-platform cluedin/cluedin-platform -n cluedin --values Cluster-Current-values.yaml

After a short time, you’ll see the confirmation of your update in the console. CluedIn is now configured to use your new DNS address.

This will use the LetsEncrypt service in the cluster to do an HTTP request to validate the certificate. If you would like to use a self-provided certificate, please review the Configure TLS Certificates page.