Deployment Examples

This chapter showcases some common deployment blueprints, but due to the configuration flexibility you deploy any blueprint you can imagine.

Recursive DNS

A Userplane with DNS Loadbalancing (dnsdist) and Recursive DNS (Recursor) could look like this:

Overview of recursive DNS configuration

To expose this Recursive DNS solution to your users, you can configure any number of protocols to do so:

Recursive DNS exposed via multiple protocols

Authoritative DNS

A Userplane with Authoritative DNS deployed via Cloud Control allows you to make use of a PowerDNS component called "Lightning Stream" which is capable of keeping data sets synchronized via the use of replicated S3 buckets. For example:

Overview of Authoritative DNS with Lightning Stream

This provides an alternative to zone transfers and is an ideal solution for distributed cloud-native Authoritative DNS deployments.

Recursive & Authoritative DNS

You can also configure a combination of both Authoritative & Recursive DNS and use ZoneControl's GUI to manage your zones & records:

Authoritative & Recursive DNS with ZoneControl

Multiple datacenters and Userplanes + Controlplane

You can also deploy multiple Userplanes and Controlplanes and configure them to create an even more comprehensive DNS solution:

Recursive DNS in 3 datacenters with a centralized Controlplane

In the above diagram you see 3 datacenters (or Kubernetes clusters) with a Userplane deployment configured for Recursive DNS with filtering enabled on dnsdist. The Controlplane fulfills 2 purposes:

• Filtering feed: Provide a feed which the dnsdist instances can use as a basis for filtering decisions
• TopN Reporter: The dnsdist instances send traffic data to TopN Reporter, which then produces reports about the traffic at set intervals