What application protocols can I use with Traffic Manager?Īs explained in How Traffic Manager Works, Traffic Manager works at the DNS level. Any increase in DNS latency should be offset by lower network latency to the endpoint. The net result is that the overall performance impact associated with this method should be minimal. The Performance method routes traffic to the closest available endpoint. In addition, caching of DNS responses means that the additional DNS latency incurred by using Traffic Manager applies only to a fraction of sessions. Traffic Manager uses a global network of name servers, and uses anycast networking to ensure DNS queries are always routed to the closest available name server. The impact of Traffic Manager on DNS resolution time is minimal. Since Traffic Manager integrates with applications at the DNS level, it does require an additional DNS lookup to be inserted into the DNS resolution chain. Since clients connect to your service endpoints directly, there’s no performance impact incurred when using Traffic Manager once the connection is established. What is the performance impact of using Traffic Manager?Īs explained in How Traffic Manager Works, Traffic Manager works at the DNS level. For endpoints using the Azure App Service, see configuring a custom domain name for a web app in Azure App Service using Traffic Manager. Make sure that the application is configured to accept the correct host header for the domain name you’re using. The HTTP host header sent from the client's browser is the most common source of problems. That includes any interaction that Traffic Manager has on the application traffic flow.įurther investigation should therefore focus on the application. For the client to connect to the application, all DNS resolution steps are complete. Therefore, any HTTP error you see must be coming from your application. Traffic Manager doesn’t see HTTP traffic between client and server. Clients then connect to the service endpoint directly, not through Traffic Manager. It uses DNS responses to direct clients to the appropriate service endpoint. Why am I seeing an HTTP error when using Traffic Manager?Īs explained in How Traffic Manager Works, Traffic Manager works at the DNS level. This limitation is common to all DNS-based traffic management systems and isn’t specific to Traffic Manager. Therefore, Traffic Manager has no way to track individual clients and can’t implement 'sticky' sessions. Therefore, Traffic Manager doesn’t see the HTTP traffic between the client and the server.Īdditionally, the source IP address of the DNS query received by Traffic Manager belongs to the recursive DNS service, not the client. Clients connect to the service endpoint directly, not through Traffic Manager. Does Traffic Manager support 'sticky' sessions?Īs explained in How Traffic Manager Works, Traffic Manager works at the DNS level. If you have endpoints that are inside a private network (for example, an internal version of Azure Load Balancer) or have users making DNS requests from such internal networks, then you can’t use Traffic Manager to route this traffic. Hence, Traffic Manager can route traffic that originates from the public internet to a set of endpoints that are also internet facing. What types of traffic can be routed using Traffic Manager?Īs explained in How Traffic Manager Works, a Traffic Manager endpoint can be any internet facing service hosted inside or outside of Azure. If you want static IP address for your service, that must be configured at the service, not in Traffic Manager. Therefore, Traffic Manager doesn’t provide an endpoint or IP address for clients to connect to. It sends DNS responses to direct clients to the appropriate service endpoint. In this article Traffic Manager basics What IP address does Traffic Manager use?Īs explained in How Traffic Manager Works, Traffic Manager works at the Domain Name System (DNS) level.

Traffic manager president edition v11