Sales (Private)

Executive Summary: Secondary and Multiple DNS

Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/947181

Contents of this Issue

Navigation

Page 1 of 1

Pros Pros Cons Cons Use Case Use Case dyn.com 150 Dow Street, Manchester, NH 03101 USA @dyn 603 668 4998 Copyright © 2018, Oracle and/or its affiliates. All rights reaserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. 1051 dyn.com 150 Dow Street, Manchester, NH 03101 USA @dyn 603 668 4998 2| Hidden Master-Secondary Option 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, but the primary DNS service maintains control from a records management perspective to all secondary services. Users Example.com? 1.1.1.1 Example.com? 1.1.1.1 Hidden Master Secondary On the side of the customer, outside the delegation. Receives updates just like a normal primary - secondary. Data Recursives Users Example.com? 1.1.1.1 Example.com? Example.com? 1.1.1.1 1.1.1.1 Primary Primary Both managing independent versions of the zone API Daemon Makes concurrent changes on both systems at all times. Recursives 3| Primary-Primary Options 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. Visit dyn.com/dns/secondary-dns to find out more. Provides added security (only supplementary DNS service is visible to the outside world). You cannot take advantage of advanced features; if the primary service suffers an outage, ability to update records is lost. Already have an existing in-house DNS solution and need added resiliency. You can take advantage of advanced features so long as both services support them; you can update DNS records from either service; you can update DNS records in the event one of the services fails. More complex to deploy or administer (you'll need to manually update both services or write an application to sync records across services). Costs of advanced features increases as you add providers. Have complex traffic steering needs and require advanced supplemental service features.

Articles in this issue

Links on this page

view archives of Sales (Private) - Executive Summary: Secondary and Multiple DNS