Best Practices for Deploying for Scale, Performance, and Resiliency

Reasoning

Resiliency and availability are key for any business. NS1’s Private DNS offering is no different. Our solution is architected to provide availability when needed and resiliency in the face of issues. An architecture designed for resiliency and availability provides a solution with minimal downtime and high availability ensuring the enterprise’s continued operation under suboptimal conditions.

Methodology

Separating the edge (cache and dns) from the core (data, web and xfr) allows publicly accessed systems to be entirely separate from the ‘moving parts’ of the system. Scaling the edge becomes trivial, allowing for increased capacity and availability while protecting the core systems.

Redundancy in the core systems allows for DR planning as well as protecting against unexpected container or host failures. Having multiple data containers in a primary-replica setup allows for failover and robust core function.

Having a geographically diverse network means lower latency for users and better performance on a global scale.

Load balancing the DNS edge containers allows for very high capacity and availability through one IP address on the edge. Ideally this configuration would monitor DNS edge containers and remove failed containers from service. Configuration of DNS load balancing is an advanced topic. Contact NS1 for information on possible solutions. 


Execution

By utilizing cache containers at the edge, each serving a number of DNS boxes, it is trivial to create an edge network with extreme capacity and vast geographic diversity. Instead of each DNS container connecting to the core data container, only the cache containers will connect to the core, vastly reducing the number of connections and reducing load on the core.

A redundant set of data container replicas can be created easily allowing for warm failover should there be an issue with the primary container. Data is replicated from the primary data container to the replica containers real-time. If a failure occur with the primary, setting one of the replica containers as primary involves a single configuration change, and the restart of a service. Please see the Data Container Failover knowledge base article for detailed information.

Request a Demo

Contact Us

Get Pricing