Root GoDaddy authentication
BMDynIP’s Web UI and cron runner run as root and invoke
/opt/prod/godaddy-cli/gddy directly for production DNS updates. Authentication
belongs to gddy, using root’s configured credentials and the inherited environment.
Verify authentication
As root, run a read-only query for your configured domain:
/opt/prod/godaddy-cli/gddy dns list osoyalce.com --type A --env prod --output json --timeout 20s
A successful response confirms read access; an empty record list is valid.
Configure root’s gddy authentication to permit DNS reads and updates. To
configure an interactive login, run as root:
/opt/prod/godaddy-cli/gddy auth login --env prod --scope domains.dns:update
Use gddy’s authentication commands to manage its credentials. If you use
environment credentials, make them available to both the Web UI service and cron
runner; variables exported in an interactive shell do not automatically reach them.
Keep tokens out of command arguments, cron entries, service logs, and the repository.
BMDynIP does not read $HOME/.godaddy-cli or /etc/bmdynip/auto.env. Existing
copies are preserved during installation, upgrades, and uninstallation.
Issues and Workarounds
I run the BMDynIP on a headless server. In order to setup GodDaddy authentication, I had to
- Run the
gddy authcommand on the headless server. - Cut-and-paste the URL to my workstation where I have a browser installed.
- On my workstation, authenticate over the web to GoDaddy.
- Capture the failed to connect URL on my workstation.
- Cut-and-paste the failed to connect URL to the server so the
gddy authcommand gets the reply.
That allowed my headless server to authenticate sucessfully.