blade/darkproxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(namecoin): switch .bit resolution to true on-chain via local namecoind RPC
Configuration validation / lint (push) Has been cancelled
Details
Configuration validation / smoke (push) Has been cancelled
Details

Browse Source
This commit is contained in:
auto-ci
2026-03-01 22:47:32 -05:00
parent 958947b334
commit d66f208f0e
3 changed files with 119 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -5
View File
@@ -158,12 +158,13 @@ python3 scripts/resolve_ens.py ens.eth --include-text --pretty
```
## Local Namecoin (.bit) resolver
## Local Namecoin (.bit) resolver (true on-chain)
`.bit` lookups are routed through a local `namecoindns` service in the stack:
`.bit` lookups are routed through a local blockchain-backed resolver path:
* CoreDNS forwards `bit.:53` to `10.5.0.12:53`.
* `namecoindns` performs DNS-over-HTTPS upstream resolution.
* CoreDNS forwards `bit.:53` to `10.5.0.12:53` (`namecoindns`).
* `namecoindns` queries local `namecoind` JSON-RPC (`10.5.0.13:8336`).
* `namecoind` syncs the Namecoin blockchain and serves on-chain records.
Quick test:
@@ -173,7 +174,10 @@ docker exec darkpihole dig @10.5.0.4 TXT id.bit
```
If your environment returns `NXDOMAIN` for `.bit`, configure Namecoin-capable
DoH upstreams in `docker-compose.yml` under `namecoindns` (`NAMECOIN_DOH_UPSTREAMS`).
records in Namecoin itself and wait for local `namecoind` sync completion.
> **Important:** initial blockchain sync can take significant time. During sync,
> `.bit` responses may be empty or incomplete.
## Monitoring the proxy