Skip to main content

Traffic Manager

Route users to the nearest (or preferred) endpoint with geo/latency‑based DNS — the DashXDNS equivalent of Azure Traffic Manager / Route 53 routing. Great for multi‑region apps.

Build a routing record​

  1. Go to Network → DashXDNS → Traffic Manager → New.
  2. Name the record (e.g. App geo‑routing); DashX generates the CNAME target (or set your own).
  3. Add pools — one per region/endpoint:
    • Name (e.g. us-east)
    • Endpoint IP
    • Geo — which clients it serves, e.g. US,CA / EU, plus a default pool as the catch‑all.
  4. Save, then copy the target and CNAME your public hostname to it.

How routing works​

DashXDNS answers each query with the pool that matches the client's location, falling back to the default pool when no geo rule matches. Combine with Failover so an unhealthy regional endpoint is taken out of rotation.

tip

Always define a default pool — clients that don't match any geo rule need somewhere to go, or they'll get no answer.