DNSalsa Connector
DNSalsa connector is a lightweight Docker container that exposes a service on your network at your own dnsalsa.nl address through a Cloudflare Tunnel.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
41/100 Fair
- Maintained
- 75last commit 19 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-11-02
- License
- MIT
- Activity
- rising
Checked 15 days ago - source: GitHub (DNSalsa/dnsalsa-docker)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Subscription and Home Assistant note The connector needs a DNSalsa account with the Remote subscription to expose services via a Cloudflare Tunnel. Without Remote it only keeps a hostname via dynamic DNS. On Home Assistant OS/Supervised, use the DNSalsa Home Assistant integration instead. source
Fetched 15 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does the DNSalsa Connector need inbound ports or port forwarding?
No, it runs a Cloudflare Tunnel to put the service online at your dnsalsa.nl address. This avoids port forwarding and keeps your home IP hidden.
How do I authenticate the Docker container to my DNSalsa account?
It pairs with a short code shown in the Web UI and logs rather than copying a tunnel token into the container.
How can an update call target only one of my IPv4 or IPv6 records?
Use the type= parameter to pick which record the call updates. A records are used for IPv4 and AAAA records are used for IPv6.
Can I review previous IP changes in DNSalsa?
Every change is logged with the time, old and new IP, and the client that sent it. This shows when your provider moved your IP or another client attempted an update.
Answers sourced from dnsalsa.nl, github.com, github.com
Community
Collected 15 days ago - public community threads