Finesse with dness: a dynamic dns client
When one has a server that is subjected to unpredictable IP address changes, such as at home or elsewhere, a change in IP address causes unexpected downtime. Instead of paying for a static IP address, one can employ a dynamic dns client on said server, which will update the WAN IP address on the dns server.
There are plenty of dynamic dns clients, including the venerable ddclient, but troublesome installation + perl system dependency resolution, and cache format errors have left much to be desired. Other solutions fall short, so dness was created with the following goals:
- ✔ Cross platform (Windows, Mac, Linux, ARM, BSD)
- ✔ Zero dependencies (one can opt to dynamically link openssl when compiling from source)
- ✔ A standard configuration (TOML) that is similar to ddclient's
- ✔ Support for multiple Dynamic DNS Services:
- ✔ Permissively licensed
To maximize initial flexibility, dness is not a daemon. Instead it relies on the host's scheduling (cron, systemd timers, windows scheduler).
- Download the latest deb
dpkg -i dness<version>_amd64.deb
# ensure it is working
/usr/bin/dness
# enable systemd timer
systemctl daemon-reload
systemctl start dness.timer
systemctl enable dness.timer
# update configuration
${EDITOR:-vi} /etc/dness/dness.conf
# create the environment variables with sensitive info
(umask 077; touch /etc/dness/dness.env)
${EDITOR:-vi} /etc/dness/dness.env- Download the latest zip with "windows" in its name
- Unzip
- Create configuration file (
dness.conf) - Execute
dness.exe -c dness.confto verify behavior - If desired, use windows task scheduler to execute command at specific times
Download the latest appropriate target
No configuration file is necessary when only the WAN IP is desired.
./dnessSample output:
[INFO trust_dns_proto::xfer::dns_exchange] sending message via: UDP(208.67.220.220:53)
[INFO dness] resolved address to 256.256.256.256 in 23ms
[INFO dness] processed all: (updated: 0, already current: 0, missing: 0) in 29ms
But dness can do more than resolve one's WAN IP. Below is a simple configuration file (conventionally named dness.conf) that will update cloudflare records.
[[domains]]
type = "cloudflare"
token = "dec0de"
zone = "example.com"
records = [
"n.example.com"
]Execute dness with the configuration:
./dness -c dness.conf
Dness will substitute in values from the environment into the configuration so that sensitive values don't need to be specified in the config:
[[domains]]
type = "cloudflare"
token = "{{MY_CLOUDFLARE_TOKEN}}"
zone = "example.com"
records = [
"n.example.com"
]This is a great way to run dness in an unprivileged account but still have access to sensitive values.
Below are the configuration options, but they've been annotated with comments.
[log]
# How verbose the log is. Common values: Error, Warn, Info, Debug, Trace
# The default level is info
level = "Debug"
[[domains]]
# We denote that our domain is managed by cloudflare
type = "cloudflare"
# Create Cloudflare token by using the use "Edit zone DNS" API token template.
# Alternatively one can use email + key fields but the token is recommended as
# it is more secure
token = "dec0de"
# The email address registered in cloudflare that is authorized to update dns
# records. Only required when not using the token field
# email = "[email protected]"
# The cloudflare key can be found in the domain overview, in "Get your API key"
# and view "Global API Key". Required when "email" is used
# key = "deadbeef"
# The zone is the domain name
zone = "example.com"
# List of A records found under the DNS tab that should be updated
records = [
"n.example.com"
]
# More than one domain can be specified in a config!
[[domains]]
type = "cloudflare"
email = "[email protected]"
key = "deadbeef"
zone = "example2.com"
records = [
"n.example2.com",
"n2.example2.com"
][[domains]]
# We denote that our domain is managed by cloudflare
type = "cloudflare"
# The email address registered in cloudflare that is authorized to update dns
# records
email = "[email protected]"
# The cloudflare key can be found in the domain overview, in "Get your API key"
# and view "Global API Key" (or another key as appropriate)
key = "deadbeef"
# The zone is the domain name
zone = "example.com"
# List of A records found under the DNS tab that should be updated
records = [
"n.example.com"
]Cloudflare dynamic dns service works in three steps:
- Send GET to translate the zone (example.com) to cloudflare's id
- Send GET to find all the domains under the zone and their sub-ids
- Cloudflare paginates the response to handle many subdomains
- It is possible to query for individual domains but as long as more than one desired domain in each page -- this methods cuts down requests
- Each desired domain in the config is checked to ensure that it is set to our address. In this way cloudflare is our cache (to guard against nefarious users updating out of band)
[[domains]]
# denote that the domain is managed by godaddy
type = "godaddy"
# The GoDaddy domain: https://dcc.godaddy.com/domains/
domain = "example.com"
# This is the api key, you can create one here:
# https://developer.godaddy.com/keys
key = "abc123"
# The password for the key, top secret!
secret = "ef"
# The records to update. "@" = "example.com", "a" = "a.example.com"
records = [ "@", "a" ]GoDaddy dynamic dns service works as the following:
- Send a GET request to find all records in the domain
- Find all the expected records (and log those that are missing) and check their current IP
- Update the remote IP as needed, ensuring that original properties are preserved in the upload, so that we don't overwrite a property like TTL.
[[domains]]
# Namecheap requires that dynamic dns is enabled in their UI!
type = "namecheap"
domain = "test-dness-1.xyz"
ddns_password = "super_secret_password"
# The records to update. Make sure they are listed as A + Dynamic DNS
# "@" = "test-dness-1.xyz"
# "* = "<any-sub-domain>.test-dness-1.xyz"
# "sub = "sub.test-dness-1.xyz"
records = [ "@", "*", "sub" ]The namecheap services requires dynamic dns enabled in their UI.
Updating the dns entry works as follows:
- A dns query is sent to cloudflare to check the IP of the record
- If the IP is different than WAN then a request is sent to namecheap to update it
- If the IP is the same, no action is taken
This method suffers from natural flow of dns propagation. When namecheap receives the update, it may take up to an hour for cloudflare to see the new record. In the meantime, dness will keep updating namecheap servers with the WAN. This has no consequential side effects other than momentary confusion why updates are being sent to namecheap every 5 minutes. Future revisions of this provider may use another method (like API integration) if the current method proves deficient enough.
[[domains]]
type = "he"
hostname = "test-dness-1.xyz"
password = "super_secret_password"
records = [ "@", "sub" ]he.net follows the same flow as Namecheap (check the current record via DNS and update if necessary).
[[domains]]
type = "noip"
hostname = "dnesstest.hopto.org"
username = "[email protected]"
password = "super_secret_password"[[domains]]
type = "dynu"
hostname = "test-dness.camdvr.org"
username = "MyUserName"
# ip update password:
# https://www.dynu.com/en-US/ControlPanel/ManageCredentials
password = "IpUpdatePassword"
# The records to update.
# "@" = "test-dness.camdvr.org"
# "sub = "sub.test-dness.camdvr.org"
records = [ "@", "sub" ][[domains]]
# denote that the domain is managed by porkbun
type = "porkbun"
# The Porkbun domain: https://porkbun.com/account/domainsSpeedy
# IMPORTANT: You must enable API Access for the domain at the above url.
domain = "example.com"
# This is the api key, you can create one here:
# https://porkbun.com/account/api
key = "abc123"
# The password for the key, top secret! Only visible once when you create the key.
secret = "ef"
# The records to update. "@" = "example.com", "a" = "a.example.com" "*" = "*.example.com"
# Both "@" and "" are valid to configure root domain.
records = [ "@", "a" ]Porkbun dynamic dns service works similar to GoDaddy:
- Send a POST request to find all records in the domain
- Find all the expected records (and log those that are missing) and check their current IP
- Update the remote IP as needed, ensuring that original properties are preserved in the upload, so that we don't overwrite a property like TTL.
There are a couple different methods for dness to resolve the WAN IP address.
The default WAN IP address resolver queries OpenDNS. It resolves IPv4 addresses by querying "myip.opendns.com" against resolver1.opendns.com and resolver2.opendns.com.
While it is the default, it can explicitly be specified by appending snippet below to the top of the config:
ip_resolver = "opendns"OpenDNS may not be available to all networks, so one can configure dness to use Ipify. Instead of using DNS, an HTTPs request will be sent. To opt into using Ipify, append the snippet below to the top of the config:
ip_resolver = "ipify"
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent