Implementing DNS

Common DNS Deployments

DNS servers are deployed worldwide in a variety of configurations. Most deployments rely on 40 year open source technologies such as Bind. However, a number of companies have worked to optimize DNS for the Enterprise application and others have pushed to provide cloud DNS services. 


The implementation of a recursive DNS server is typically the same, regardless of which technology is deployed. Local hosting of DNS typically includes dedicated hardware (physical or virtual) that runs the service. All queries point to these servers to provide the lookup response. The advantage of local hosting is increased control of query management and potentially lower latency response time.

Cloud DNS implementations provides a similar service, but its architecture is distributed with a reverse proxy, sending queries to the appropriate DNS server. The advantage of using a cloud service is that infrastructure setup or management is not needed.

Local + Cloud Hybrid

ThunderDNS architecture

Thunder DNS is a hybrid of Local and Cloud DNS.


Our image is installed on a local server in the Data Center or on the network edge. This placement enables low latency response time and maximum control over the DNS architecture. 


Our Cloud component resides on servers distributed all over the world and supports local DNS instances. For example, our Cloud updates in real time to new security threats and provides a check system for local queries requiring further investigation. 

Advantages of deploying Thunder DNS

Below are some of the reasons to deploy Thunder DNS instead of alternative solutions:

1. Deploys in less than 30 minutes (easy installation process and intuitive GUI)  

2. Cloud + Local Hybrid Architecture (automatic updates of security definitions)

3. Virtual Image can be installed on existing DNS hardware

More Technology