This release is a pre-release and may not be stable for production use.
CompactDNS (CDNS)
CompactDNS (CDNS) is a minimalistic yet powerful DNS server designed for simplicity and speed, offering local caching, as well as authoritative, recursive, and forwarding capabilities.
In 2025, Google Chrome will remove adblockers with the impending Manifest V3 update. This change threaten the existance of software like UBlock Origin. Rather than abandoning Chrome, I explored alternative ways to block ads. This DNS server, CompactDns, was the result: it's lightweight, blazing fast, and can block ads. It also caches all requests on device, leading to a latency as low as 0 ms.
- ninjamar
Installation
Install CDNS
pip install cdns
CDNS can also be installed from source
git clone https://github.com/ninjamar/compactdns
cd compactdns
pip install .
For development,
pip install -e .
Usage
After installation, CDNS can be used by running:
cdns [command] [options]
The server can be run as a daemon, or as a standalone program.
Running the Server
To start the server:
cdns run [options]
Configuration is stored in a toml or json file. See config.toml for an example configuration.
cdns run --config config.toml
The DNS protocol is typically run over port 53 for TCP and 853 for TLS.
When TLS is used, a key and certificate file are required.
Generate a pair:
openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes
Configuration
An example configuration file is available in config.toml.
Running as a Service
MacOS / OSX
CDNS can be set up to run in the background as a service:
sudo cdns install -c /path/to/config
This command will output instructions for starting and stopping the server.
Startup logs are written to /tmp/cdns-startup.log and cdns-startup-err.log .
[!NOTE] MacOS seems to occasionally be killing the server when the device wakes from sleep. A program called
sleepwatcheris required to fix this.
Ensure that all paths in the configuration file are relative to the path of the configuration file.
Changing the System DNS Server
CDNS can be configured as the system DNS server. Replace A.B.C.D with the address of the server.
On MacOS:
networksetup -setdnsservers Wi-Fi A.B.C.D
DNS Zones
Zones can be stored in 3 formats:
- Single zone Json file (e.g.,
*.json) - Multiple zones JSOn file (e.g.,
*.all.json) - Traditional zone file (e.g.,
*.zone)
See the example-zones/ directory for examples.
From a Host File
To convert a host file to a JSON list:
cdns tools h2j /path/to/host.txt /path/to/output.all.json
example-zones/lowe.all.json was generated from Peter Lowe's adservers list using this script
Preload Files and Cache Dump
A preload file is a plain text list of hosts to be loaded into the cache before server startup.
# These sites will all be preloaded
google.com
github.com
example.com
The cache (and also the zones) can be written to a file upon server shutdown and reloaded on startup.
Architecture
When in recursive mode, the server can achieve latency as low as 0 ms. Initially, cache misses will result in higher latency, but once requests are resolved, responses are cached for the future.
graph TD;
send["Send the request"]
done["Response sent back"]
send --> recv["Server receives the request"]
recv --> is_cache["Is the request in the cache?"]
is_cache --> |"Yes"| cache["The request is in the cache"] --> done
is_cache --> |"No"| recursive["Recursively fulfill the request"]
recursive --> |"Add response to cache"| done
Other Commands
shell
CDNS includes an interactive debugging shell.
[!WARNING] This feature exists for debbuging. Use at your own risk
[!NOTE] Incoming requests are blocked when in use
Run the shell:
cdns shell [options]
Options:
--host,-h: The host address for the shell server ina.b.c.d:portformat
The shell opens a Python REPL connected to the main server process.
List the available commands:
>>> help(self.command)
Testing
Some outdated tests exist in tests/ directory
Instead, send test queries using dig.
dig @A.B.C.D -p PORT example.com
License
This project is licensed under the MIT License. See the LICENSE file for details.
Metadata
Release files for compactdns 0.1.0a6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| compactdns-0.1.0a6.tar.gz | 42.6 kB | Without provenance | Details for compactdns-0.1.0a6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| compactdns-0.1.0a6-py3-none-any.whl | Python 3 | none | any | Details for compactdns-0.1.0a6-py3-none-any.whl |
Total release size: 107.0 kB
Release files / compactdns-0.1.0a6.tar.gz
| Download URL | compactdns-0.1.0a6.tar.gz |
|---|---|
| Size | 42.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
637ae0ec1732be8f55dfb7f21c286d7bc0d0a2f200883ae49557c2293a1b66eb
|
|
BLAKE2b-256 checksum How to use checksums |
99d22ad9320fdc07e2afafd60c046a0b267f9e4eb5730c2d38ea155ec7adde4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Release files / compactdns-0.1.0a6-py3-none-any.whl
| Download URL | compactdns-0.1.0a6-py3-none-any.whl |
|---|---|
| Size | 64.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
216d854ba268a7961acf91a63173a9483f96ae8203d60361cd1d03f1c2786de5
|
|
BLAKE2b-256 checksum How to use checksums |
e69edbc6c195b28b790b1b112482b2cd7b7763b2b21d8d5cca50cddecc0ff150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Security for compactdns 0.1.0a6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.