Documentation Index

Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt

Use this file to discover all available pages before exploring further.

DNS entries

  • 2 minute(s) read
Prev Next

This article lists the Azure Private DNS zone entries required for each component in the Turbo360 private networking setup. These records are created when you add a private endpoint or connect a resource to an Azure Monitor Private Link Scope (AMPLS).

Overview

In a Turbo360 private deployment, all platform components resolve to private IP addresses rather than public endpoints. Azure achieves this through Private DNS Zones — one per service type — that map each resource's public hostname to its private endpoint IP. This article lists every zone and A record that must be present for the deployment to function correctly.

Business value

Correct DNS configuration is the foundation of private networking. Missing or misconfigured zones cause connectivity failures that are difficult to diagnose without a clear reference. This article gives your network team the exact zones and records to verify after deployment.

How it works

When you add a private endpoint to an Azure resource, Azure automatically creates an A record in the corresponding Private DNS Zone, mapping the resource's public FQDN to its private IP address. Clients inside the VNet resolve the hostname through Azure DNS, which returns the private IP instead of the public one. For Azure Monitor resources connected via AMPLS, the zones and A records are created when you link the workspace or Application Insights resource to the scope.

App Service (web app + function apps) — private endpoint (inbound)

  • Zone: privatelink.azurewebsites.net

  • A records: one per app, created when you add the private endpoint

    • turbo360 web app → private IP of the app's PE

    • processor function app → private IP

    • documenter function app → private IP

    • chart gen function app → private IP

App Service (web app + function apps) — private endpoint (deployment)

  • Zone: privatelink.scm.azurewebsites.net

  • A records: one per app, created when you add the private endpoint

    • turbo360 web app → private IP of the app's PE

    • processor function app → private IP

    • documenter function app → private IP

    • chart gen function app → private IP

Azure SQL — private endpoint

  • Zone: privatelink.database.windows.net

  • A record: sqlservername → private IP of the SQL private endpoint

Storage (Blob) — private endpoint

  • Zones:

    • privatelink.blob.core.windows.net

    • privatelink.file.core.windows.net

    • privatelink.queue.core.windows.net

    • privatelink.table.core.windows.net

  • A record: storageaccountname → private IP of the Blob private endpoint

Depending on what you have enabled, you will typically have the following zones:

  • Zone: privatelink.applicationinsights.azure.com (ingestion)

    • A record: regional-ingestion-name → private IP (created by the PE/AMPLS link)

  • Zone (optional, for Live Metrics): privatelink.live.applicationinsights.azure.com

    • A record: created by the private link/AMPLS

For agent/HTTP ingestion via Private Link (typically via Azure Monitor Private Link Scope):

  • Zone: privatelink.oms.opinsights.azure.com (agent ingestion)

  • Zone: privatelink.ods.opinsights.azure.com (Data Collector API / HTTP ingestion)

  • Zone: privatelink.monitor.azure.com (metrics/monitor endpoints)

  • Zone (sometimes): privatelink.agentsvc.azure-automation.net (agent service bootstrap)
    A records for each zone are created when you connect the workspace or Application Insights resource to your AMPLS.