Ken Schiano
69fa61bfd3
- root cause: Technitium image ships /etc/dns as a real directory, so the build-time 'ln -sf /data/dns /etc/dns' created the symlink INSIDE it (/etc/dns/dns) instead of replacing it. Technitium kept writing to the ephemeral container directory and lost everything on restart. - fix: add entrypoint.sh that runs at container start (after HA mounts volumes), removes the real /etc/dns dir, and symlinks it to /config/dns (the persistent addon_config mount). Seeds defaults on first run only. - bump version to 15.4.2
Hassio_Addons
Home Assistant add-on repository hosting the Technitium DNS add-on.
Add-ons
| Add-on | Description |
|---|---|
| technitium_dns | Technitium DNS Server — local DNS with ad-blocking, web console, acts as secondary to a primary Technitium instance in Kubernetes via DNS Replication |
Add this repository to Home Assistant
Settings → Add-ons → Add-on Store → ⋮ (top right) → Repositories
https://git.kenschiano.net/kschiano/Hassio_Addons.git
Then refresh the add-on store and install Technitium DNS.
Repo layout
Hassio_Addons/
├── repository.yaml # repository manifest (read by HA)
└── technitium_dns/
├── config.yaml # add-on metadata, ports, schema
├── Dockerfile # thin layer on technitium/dns-server:latest
└── README.md
Update workflow
- Bump
versionintechnitium_dns/config.yaml. - Commit and push to
git.kenschiano.net/kschiano/Hassio_Addons.git. - In Home Assistant: refresh the add-on store, update the add-on, rebuild.
Notes
- The add-on uses the upstream
technitium/dns-serverimage directly — no custom build pipeline needed. - Config persists to the add-on config volume (
/data/dnssymlinked to/etc/dns). - For primary/secondary replication setup, see
technitium_dns/README.md.