Blog Post

Azure Networking Blog
7 MIN READ

Azure DNS + Traffic Manager linked records

atiy's avatar
atiy
Icon for Microsoft rankMicrosoft
Aug 26, 2026

Introduction

Traffic Manager linked records creates a direct, managed link between an Azure DNS record set and a Traffic Manager profile. When a query arrives, Azure DNS evaluates the linked Traffic Manager profile internally and returns the appropriate endpoint response directly. For A and AAAA records, this means the client receives endpoint IP addresses without an intermediate CNAME response to trafficmanager.net.

This practical guide uses a small multi-region Contoso scenario to explain the architecture, configure the feature in the Azure portal, validate the DNS response, and demonstrate endpoint failover. The feature is currently in public preview, so the walkthrough should be tested in a non-production environment before broader adoption.

Note: DNS-based global routing is powerful, but the traditional integration between a custom domain and Traffic Manager adds an intermediate name that customers must understand, resolve, and govern.

The scenario and the problem

Contoso operates a public application across North America, Europe, and Asia. Users browse to contoso.com. Azure Traffic Manager monitors the regional endpoints and selects the preferred healthy destination according to the profile routing method.

  • Traditional CNAME integration can expose the intermediate trafficmanager.net name in the DNS response.
  • A CNAME cannot be placed at the zone of apex, which makes root-domain routing harder.
  • An unsigned intermediate DNS hop can interrupt end-to-end DNSSEC validation.
  • Operations teams must understand which system is authoritative for the customer zone, and which system makes the routing decision.

Design objective

Preserve Traffic Manager routing methods, endpoint health monitoring, and automatic failover while returning the effective endpoint answer directly from Azure DNS.

The solution: Traffic Manager linked records

Figure 1. Traditional CNAME resolution compared with Traffic Manager linked record.

As you see in figure 1 above, the left side shows the traditional path. The client queries the application name in Azure DNS, receives a CNAME that points to a trafficmanager.net profile name, and then performs another lookup before receiving the selected endpoint address. The right side shows the linked-record path. Azure DNS remains authoritative for the Contoso zone, consults the linked Traffic Manager profile internally, and returns the selected endpoint directly.

The key point is that the Traffic Manager still performs the routing decision and health evaluation. Linked records change the DNS integration and the answer returned to the client; they do not turn Traffic Manager into a reverse proxy or place it in the application's data path.

Reference architecture

Figure 2. Practical multi-region architecture for testing direct resolution and failover.

Reference architecture in figure 2 above shows the client queries contoso.com. Azure Public DNS hosts the authoritative zone and contains a record set linked to the tm-profile Traffic Manager profile. The profile uses a configured routing method and continuously evaluates the health of the regional endpoints. Azure DNS uses the Traffic Manager decision and returns the effective endpoint answer to the client.

For a simple lab, two endpoints are enough. Configure the first endpoint with priority 1 and the second with priority 2. The third regional endpoint in the diagram illustrates how the same design scales to additional regions. The record set can be created at the zone apex by leaving the record name empty, or for a subdomain such as www.

Note: Traffic Manager is DNS based. After name resolution, the client connects directly to the selected public endpoint. Application traffic does not pass through the Traffic Manager.

Prerequisites

  • An Azure subscription and permissions to create or update Azure DNS and Traffic Manager resources.
  • A public domain hosted in Azure DNS and delegated to the Azure DNS name servers.
  • Two public application endpoints that can return visibly different responses for failover testing.
  • The Microsoft.Network resource provider is registered in every subscription that contains the DNS zone or Traffic Manager profile.

Implementation in the Azure portal

The portal workflow has two main parts: create a strictly typed Traffic Manager profile, then create an Azure DNS record set that links to that profile.

Create the Traffic Manager profile

Step1: Open Traffic Manager profiles, select create.

Step 2: Configure the profile and instance details, fill out the subscription, resource group, name(tm-profile), routing method: priority, record type: A, and resource group location.

Step 3: Add endpoints (Add tmendpoint-1 as the public IP address and external endpoint type with priority 1.

Step 4: Repeat Step 3 to add the secondary endpoint (Add tmendpoint-2 as the public IP address and external endpoint type with priority 2)

Step 5: Confirm endpoint health (Wait until both endpoints report online before testing DNS behavior.)

Note: The record type selection creates a strictly typed profile. Select A for IPv4 answers, AAAA for IPv6 answers, or CNAME for canonical-name answers. The type is used to validate compatibility between the Traffic Manager profile and the linked DNS record.

Create the linked record in Azure DNS

Step 1: Open the Azure DNS zone, select the zone that hosts the application domain, for example contoso.com.

Step 2: Add DNS record sets, select + record set.

Step 3: Choose the record name, leave name empty for the zone apex or enter www for a subdomain.

Step 4: Choose the type, select the record type that matches the Traffic Manager profile, for example, A.

Step 5: Enable Traffic Management, select Enable Traffic Management (Preview).

Step 6: Select the profile, choose the profile subscription and tm-profile, then save the record set.

Note: The record set contains a managed association to the Traffic Manager profile. The linked record inherits its TTL from the Traffic Manager profile.

In the Azure DNS record list, the new record should appear as a linked record associated with the Traffic Manager profile. For an apex A record, the conceptual result is:

Validate the DNS response

Use both the Azure portal and direct DNS query. The portal confirms the resource association; the DNS query confirms the serving behavior.

Portal validation

  • The record exists in the expected Azure DNS zone.
  • The record type matches the strictly typed Traffic Manager profile.
  • The linked profile is tm-profile.
  • The Traffic Manager endpoints show their expected health state.

Command-line validation

 

A successful A-record test returns the selected healthy endpoint IP address and does not include a trafficmanager.net CNAME in the answer. Querying for an Azure DNS authoritative name server directly is useful during testing because it reduces ambiguity from local recursive resolver caches.

The specific endpoint returned depends on the routing method, endpoint health, source resolver location, and cached TTL behavior. Validate the result against the profile configuration rather than expecting one universal IP address.

Prove automatic failover

A practical demonstration should show that the linked record is not static. The returned answer continues to reflect Traffic Manager health decisions.

Step

Portal action

What to configure

1

Browse to contoso.com

Confirm the priority 1 endpoint serves the application.

2

Stop priority 1 endpoint

Uncheck the enable endpoint config in tm-profile or stop the VM

3

Monitor Traffic Manager

Wait until the endpoint status changes to unhealthy.

4

Clear local cache

On Windows, run ipconfig /flushdns before querying again.

5

Query or browse again

Confirm the priority 2 endpoint is now selected.

6

Restore the primary endpoint

Start the endpoint and confirm it returns to online.

Why this matters for real architecture

Cleaner DNS answers

The client receives the effective endpoint result directly instead of resolving an intermediate trafficmanager.net name.

Zone-apex routing

Linked records can be used at the root domain, where DNS standards do not allow a CNAME record.

DNSSEC compatibility

Keeping resolution inside Azure DNS removes the unsigned intermediate trafficmanager.net hop from the customer response chain.

Operational type safety

Strictly typed profiles help ensure that the linked DNS record type and Traffic Manager endpoint response type remain compatible.

Preserved routing intelligence

Traffic Manager routing methods, endpoint monitoring, and automatic failover continue to determine the selected endpoint.

Preview and operational considerations

  • Treat the feature as preview and review the Microsoft Azure preview supplemental terms before production use.
  • Confirm that the DNS zone and Traffic Manager profile subscriptions have the required resource provider registration.
  • Plan the record type before creating the Traffic Manager profile because the strictly typed profile value cannot be changed after creation.
  • Remember that the record TTL is inherited from the Traffic Manager profile.
  • Test routing, endpoint health, DNSSEC behavior, zone-apex resolution, and rollback in a controlled environment.
  • Document the previous DNS record so the change can be reversed if the validation plan fails.

Conclusion

Traffic Manager linked records is a focused DNS improvement with meaningful architectural impact.

The feature keeps Azure DNS authoritative for the customer domain, preserves Traffic Manager health-aware routing, and removes the need for the client to follow an intermediate trafficmanager.net hop. That creates a cleaner DNS response path and enables scenarios that were difficult with a traditional CNAME, especially zone-apex routing and DNSSEC-protected domains.

The strongest way to evaluate the feature is through a small, observable lab: create a strictly typed profile, link an Azure DNS record, query the authoritative DNS server, and deliberately fail the primary endpoint. When the DNS response changes to the secondary healthy destination without exposing an intermediate Traffic Manager name, the value becomes immediately clear.

 

Final takeaway

A small change in DNS integration can simplify the client experience without giving up Traffic Manager routing intelligence, monitoring, or failover.

 

I hope you enjoyed it!

 

References

 

                                            Visual note: Figures in this document were generated with Microsoft Copilot for explanatory use.

Updated Aug 25, 2026
Version 1.0
No CommentsBe the first to comment