A Node.js-based daemon that refreshes Azure DNS records based on the detected WAN IP of the local network to the executing device. Useful for maintaining up-to-date DNS records which are pointing networks whose WAN IPs are dynamic in nature (think home networks).
See full Azure configuration instructions in
doc/installation.md.
TL;DR: Create a service principal and assign it the DNS Zone Contributor role (or the more restrictive role outlined by the included dns-record-contributor.json role definition). Then, run the Docker image with docker run (sample below) or docker-compose example available in the installation documentation.
docker run -e AZURE_SUBSCRIPTION_ID="" -e TENANT_ID="" -e CLIENT_ID="" -e CLIENT_SECRET="" -e CRON_REFRESH_INTERVAL="0 * * * *" -e RESOURCE_GROUP_NAME="" -e ZONE_NAME="" -e RELATIVE_RECORD_SET="" -e RECORD_TYPE="" esqew/azure-dynamic-dns
Currently, the script is pegged to the WAN IP echo service at https://icanhazip.com. This presents several potential issues (among others) over the longer-term:
- The service can disappear or cease to function as expected at any time (for example, the relatively recent decommissioning of the WhatIsMyIPAddress.com API)
- A given IP echo service can be inaccessible or otherwise non-functional in certain geographic regions due to routing issues, deliberate blocking of the services within corporate networks or certain geopolitical areas (i.e., China)
To mitigate these potential pitfalls, better configuration of the provider should be possible on an instance-by-instance basis.
There's currently no support for IPv6 addresses or AAAA DNS records. With the (slow) global uptake of IPv6 over time, future-proofing this daemon with this support shouldn't be too much of a lift.
This package is licensed under the MIT License. See LICENSE.md for more information.