Choosing a public DNS resolver today is about much more than picking between Google and Cloudflare.
There are dozens of public DNS services: global and regional providers, commercial services, non-profits, and community-run projects. They differ in privacy policies, filtering capabilities, DNSSEC support, encrypted DNS protocols, infrastructure locations, and logging practices.
Comparing all of them can be difficult.
Under the hood: IPv6, AMD EPYC™, DDR4, NVMe SSD storage, and a high-speed network. A strong candidate for passing OpenBLD’s stress test.
Last year, Onehost.kz supported the OpenBLD project by providing a VPS server in Almaty. Since then, the infrastructure has demonstrated stable 99.99% uptime, with no noticeable overselling or system freezes.
The solution is available for On-Premise deployments and is designed for organizations that require detailed DNS analytics, full control over their data, and event storage within their own infrastructure.
Centralized DNS event collection with ClickHouse and VictoriaLogs integration.
Malware and botnets use Domain Generation Algorithms (DGA) to generate hundreds or thousands of short-lived domains for communication with command-and-control infrastructure.
An attack example from real OpenBLD logs:
s-dfgfd-sdfz...zdssragv[.]mom96bccebb2f7e...wu7y6z[.]com60r...60pg0131[.]ccBeyond their malicious purpose, this chaotic DNS traffic pollutes resolver caches, increases CPU and I/O usage, and generates large volumes of low-value logs. At scale, it can cause higher resource consumption and degraded DNS performance.
We’ve become used to relying on DNS from Google, Cloudflare, and other large public DNS providers.
They are fast, convenient, and easy to use. But in the age of AI, large-scale data aggregation, and user profiling, convenience should not come at the cost of privacy.
OpenBLD.net takes a different path.
We are building an independent DNS ecosystem designed to reduce dependency on centralized DNS providers and give users more control over how their DNS traffic is resolved, filtered, and protected.
promppctl.sh is a native Linux installer and lifecycle helper for Deckhouse Prom++.
It installs Prom++ without Docker, creates a systemd service, can safely migrate an existing Prometheus TSDB copy, can perform release updates from GitHub Releases, and can roll back to the original prometheus.service.