As more customer, employee and partner interactions depend on web-based applications and services, DNS plays a critical role in connecting users to content; and if your DNS fails you don’t exist—digitally speaking, that is. Secondary and more broadly multi-DNS provides a cost-effective insurance policy against DNS failure, one you can’t afford to be without. And because all DNS services respond in multi-DNS architectures, the performance of resolution will also improve. Secondary or Multi-DNS is a robust DNS architecture using more than one DNS solution to promote business continuity and optimal DNS resolution performance.
Key Secondary / Multi DNS Deployment Patterns
The existing DNS implementation acts as the primary DNS service from a DNS records management perspective. Record updates are made to the primary service using established tools and practices. Once configured, the primary service automatically updates the secondary service using the standard DNS NOTIFY mechanism. Secondary DNS service receives updates via standard IXFR or AXFR. Both services respond to DNS queries.
Hidden Master Secondary
The existing DNS solution is deployed behind the corporate firewall and acts as the primary DNS service from a DNS records management perspective. Record updates are made to the primary service using established tools and practices. The primary service automatically updates the secondary service. Only the distributed edge of the secondary takes traffic. An additional supplementary service may be added to extend global performance and resiliency.The primary DNS service maintains control from a records management perspective to all secondaries.
Each DNS service is updated independently. Records are synchronized across services manually, with the API, or via an external application. Both services respond to DNS queries.