Search Results

Depending on the client's network topology, there can be numerous deployment schemes. Below are examples of typical solutions. For ISPs This deployment option is used in large networks where end users are behind NAT in relation to the client's main equipment...

To apply various filtering policies and to separate statistics by requests, it is necessary to identify the end user. In the on-premises solution, user identification is achieved through one of the following methods: IP IP/subnet IP:port IP:[port]-[port]...

Our solution consists of the following components: DNS Proxy Module: Receives DNS requests and returns responses in the form of IP addresses. Internal Database: Stores information about all users and filtering policies. RestAPI: Used to update the Datab...

Custom Local Deployment All setup, maintenance, and support are handled exclusively by SafeDNS specialists, which clearly defines the areas of responsibility between SafeDNS and the client. The client provides the hardware (a server with x64 architecture) acc...

Binary logs are stored on the SafeDNS Security server. Our solution includes a module that parses these logs and exports them to an external DBMS for further analysis and report generation. Currently, there is a connector for exporting logs to the ClickHouse D...

The minimum system requirements for a server running the SafeDNS Security module are as follows:DNS proxy CPU requirements: Intel 12+ Gen, Intel Xeon Silver/Gold, or similar performance AMD Ryzen/Epyc For handling up to 1,000 queries per second: CPU: ...

ll interaction with SafeDNS Shield is performed via a REST API, which typically responds on port 8080 from the same IP address that handles user requests. By default, the API only responds to requests from whitelisted IP addresses specified during the server d...