Skip to main content

Setup and requirements

Product setup and support

Custom Local Deployment

All setup,Setup, maintenance, and support for an on-premises deployment are handledmanaged exclusivelyentirely by SafeDNS specialists, whichestablishing clearlya definesclear the areasdivision of responsibility between SafeDNS and the client.responsibilities. The client provides the required hardware (aand server with x64 architecture) according to the requirements, along withfull remote access to the server,access, after which weSafeDNS handleperforms the fullcomplete setupturnkey "turnkey".installation.

OurFollowing specialists,deployment, inSafeDNS collaborationspecialists work with the client,client carryto outconfigure the initial configuration of filtering rules and provide training forto enable the client'client’s staff forto make future adjustments.

adjustments

Ifindependently. needed, aA dedicated support line is made available for clients using On-Premon-premises solutions.

VM deploymentDeployment via ISO Image

As

an
alternative
to
a
physical

Theserver installationinstallation, SafeDNS Shield can also be donedeployed usingas ana virtual appliance by mounting the provided ISO image mounted in a virtual machinemachine. This method streamlines deployment in environments that rely on virtualization infrastructure.

System requirements

The following specifications apply to a server running the SafeDNS Shield components. All deployments require Debian 12 (VM)x86‑64).

DNS Proxy Module

Choose a configuration based on the expected peak query load.

CPU: Intel 12th‑generation or later, Intel Xeon Silver/Gold, or equivalent AMD Ryzen/Epyc.

Queries per second (QPS) CPU Cores RAM Storage Network Up to 1,000 4 8 GB 200 GB NVMe 1 Gbps Up to 15,000 12 16 GB 512 GB SSD (RAID 1) 1 Gbps Up to 310,000 64 128 GB 2 TB SSD/NVMe (RAID 1) 1 Gbps Up to 2,000,000 128 2 TB 16 TB SSD/NVMe (RAID 1) 25 Gbps
ClickHouse Cluster (Statistics Storage)

The ClickHouse cluster stores and analyzes DNS request logs. A single node meets the following minimum:

    CPU: 6 cores (x86‑64) RAM: 16 GB Storage: 500 GB NVMe
      Expandable up to 6 TB depending on traffic volume and retention needs

      Example configuration for 75,000 QPS and one year of log retention:

        4 ClickHouse data nodes
          CPU: 6 cores RAM: 16 GB Storage: 6 TB NVMe 3 ClickHouse Keeper nodes (coordination service)
            CPU: 2 cores RAM: 4 GB Storage: 60 GB SSD

            We recommend a minimum cluster of 4 data servers arranged as 2 shards × 2 replicas. This provides parallel read/write operations and redundancy. A load balancer distributes incoming statistics across the nodes.

            For lower traffic volumes, a standalone ClickHouse server can be deployed without ClickHouse Keeper, eliminating the need for the coordination layer.