Configure public DNS

Complete this step when:

• public access is enabled; and
• you selected a company-owned DNS domain during deployment.

If you use the platform-provided DNS domain, use the hostnames provided in the Your deployment is ready notification and no customer DNS records are required unless specifically instructed.

Before you begin

Use the endpoint and DNS information provided for your deployment.

Depending on the enabled services, this can include hostnames for:

• Elasticsearch;
• Kibana;
• Fleet.

Do not construct DNS targets from Azure resource names or naming conventions.

Create the DNS records

For each service hostname:

1. Open the authoritative DNS service for your company-owned DNS domain.
2. Create the DNS record using the hostname and target provided by the platform.
3. Save the record.
4. Allow time for DNS propagation.

Use the record type and target provided by the deployment information.

Verify DNS

From a client that uses public DNS, verify each service hostname.

nslookup <service-hostname>

Confirm that the hostname resolves to the expected platform target.

Repeat the check for each endpoint you plan to use.

Next step

After DNS resolution is working, continue to configure TLS certificates when a customer certificate is required.

Then verify access.

If the hostname does not resolve as expected, see connectivity issues.