dness

This release is for the sysadmins out there. The dness config file is now treated as a handlebar template with variables filled in from the environment. Now one can write

[[domains]]
type = "cloudflare"
token = "{{MY_CLOUDFLARE_TOKEN}}"
zone = "example.com"
records = [
    "n.example.com"
]

And if MY_CLOUDFLARE_TOKEN is in the environment then dness can be executed as an unprivileged, dynamic user. This mainly affects systemd users who will now want to extract sensitive info into:

/etc/dness/dness.env

and format it like so:

MY_CLOUDFLARE_TOKEN=dec0de

Also for systemd users, the provided service file now sandboxes dness properly.

This release also consolidates the x86 linux builds to only builds that are built with musl with openssl statically compiled. This should be a minor annoyance. Those that want everything dynamically linked are encouraged to build from source, and users of the musl deb variant (myself included) will need to migrate to the new deb with:

dpkg --remove dness-musl
dpkg --install dness_0.5.0_amd64.deb

• Fixed an issue with the static builds not being deployed to github issues. No code changes.

• Slight change to log entries
• Musl (static builds) releases now bind to rustls instead of openssl
• Add Namecheap provider
• Internal dependencies updated

• Add GoDaddy provider
• Bump serde_json from 1.0.34 to 1.0.36
• Bump reqwest from 0.9.7 to 0.9.8

This is the initial release of dness -- and it is currently only an MVP (minimal viable project). Dness does one thing: detect WAN IP through OpenDNS and update the appropriate records on Cloudflare. But already at v0.1.0 it has scratched my itch; solved a problem I had with the current array of dynamic dns clients, so I decided to release it -- not in the thought that dness will be some de facto dynamic dns client, but that if dness solved a problem I had, maybe it will solve others' problems.

With that said, there here are a list of improvements that can conceivably be implemented:

• Support dynamic dns in the truest / traditional sense of the phrase by supporting rfc2136 (DNS Update)
• Support additional dns hosts (eg: namecheap)
• Support additional ip resolvers (eg: http://httpbin.org/ip)
• Multiplex requests / operations using tokio
• Allow daemon mode so dness is more self contained
• Additional packaging (APT / yum repos)
• Configurable logging (ie: json) to be flexible enough to meet any logging needs