nightah/godaddy-dyndns

godaddy-dyndns⁠ is a DynDNS-like public IP auto-updater script for GoDaddy, written in Python.

The script uses ipify.org to figure out the machine's public IP. It will only access GoDaddy if the IP has changed since the last successful script invocation. It logs all its activities to the file /config/godaddy-dyndns.log and automatically rotates the log.

Based on a modified version of CodeCorrupt's script⁠.

Usage

docker create --name=godaddy-dyndns \
-v <path to data>:/config \
-e PUID=<uid> -e PGID=<gid> \
-e TZ=<timezone> \
nightah/godaddy-dyndns

Parameters

The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a volume -v external:internal - what this shows is the volume mapping from internal to external of the container. So -v /mnt/app/config:/config would map /config from inside the container to be accessible from /mnt/app/config on the host's filesystem.

• -v /config - local path for godaddy-dyndns config files
• -e PUID for UserID - see below for explanation
• -e PGID for GroupID - see below for explanation
• -e TZ for setting timezone information, eg Australia/Melbourne

It is based on alpine linux with s6 overlay, for shell access whilst the container is running do docker exec -it godaddy-dyndns /bin/bash.

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work".

In this instance PUID=1001 and PGID=1001. To find yours use id user as below: $ id <dockeruser>uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Info

• To monitor the logs of the container in realtime docker logs -f godaddy-dyndns.

Version

• 03/01/18: Initial Release