Modules

The Route solution consists of the following modules:

• Managed (Primary) or Secondary DNS
• DNS Health Checks

Managed (Primary) or Secondary DNS Module

This module allows:

• DNS zone management capabilities through which various types of records (e.g., A, AAAA, CNAME, etc.) may be added to a zone.
• Authoritative DNS for a zone managed outside of our network. Our DNS service maintains a synchronized copy of that zone through secondary zoneIdentifies a zone that is a copy of a zone that is managed outside of our network. This type of zone is automatically synchronized to match any changes performed to the source zone. Our DNS service is authoritative for all secondary zones.s.
• Traffic to be distributed across multiple web servers via load balancingIndicates the capability to distribute requests between multiple web servers or domains. or failoverIndicates the capability to redirect all traffic to a backup server/domain when the primary one is deemed unfit to resolve requests..

This module contains the following components:

Component	Description
Standard Routing	This component is applicable to all zones that do not leverage our load balancing/failover capabilities or advanced policies.
Adaptive Availability	This component allows traffic management (i.e., load balancing or failover) for: Address or CNAME records of a primary zone hosted by our Route solution. A CNAME record or subdomain of a primary zone hosted by another DNS service provider. This module excludes zones on which advanced policies have been applied. Once an advanced policy has been applied to a zone, it falls under the Advanced Policy Routing component.
Advanced Policy Routing	Identifies zones that leverage advanced policies that allow routing based on IP address, country, ASN, IP groups, network groups, POP, or IP type. This type of zone can also leverage our load balancing/failover capabilities. Advanced policy setup requires the engagement of our Professional Services team.

DNS Health Checks Module

The health of a server/domain that is part of a load balancing or failover configuration can be probed by polling it with an HTTP or TCP request. If the majority of our servers deem it to be unfit to serve traffic, then this module will take the following action:

• Load Balancing: If a server/domain is deemed unhealthy, it will be pulled out of load balancing and traffic will be redistributed proportionally to the remaining healthy servers/domains.
• Failover: If the primary server/domain is deemed unhealthy, all traffic will be switched to the backup server/domain.

Edgecast CDN