Best Practice principles for DDI architectures aim at security and resilience across a distributed network of connected servers, with:
Redundancy and elimination of a single point of failure- Physical separation of different roles within the architecture
Building on the orthodox master-slave approach built into the DNS protocol is a good starting point for achieving these goals.
The DNSBOX range was designed to make this approach easy and affordable. So it includes a variety of appliance models and options, each designed for a specific purpose within an overall architecture:
- Central management “master” appliances with powerful DDI management software, and fully integrated DDI and dedicated DNS options
- Connected server ultra-secure “slave” appliances for DNS slave, recursive resolver (DNS cache) and DHCP server roles
- Options to include just the services you need on both central master and remote servers
- Multiple options for redundancy, including failover units of central master and connected server appliances
- A choice of different hardware platforms for each component to fit the size of the job
This allows tailored solutions with specific models and options chosen to fit each customer requirement closely and do the particular task required very well. As a result:
- The solution should be simpler, because un-necessary functionality is cut out in each component appliance.
- Because each component is designed for a specific task, it does that task well.
- Purpose-built devices for each tasks means lower cost. You don’t have to pay for features you don’t need.
- You can easily add layers of security and redundancy to match risks and budgets.
- Scalability is easy and low-cost.
 |