OPNsense Forum
English Forums => Tutorials and FAQs => Topic started by: BISI Sysadmin on December 24, 2022, 08:18:24 am
-
... or at least a web link where I can check every so often?
I have been using dyn.com since they had free accounts (and were called dyndns.org), sometime around the turn of the century. Anyway, I have quite a large number of clients supported through my account at dyn.com, and I'm getting pretty antsy at the warning that support for os-dyndns is about to be terminated.
I have tried and failed several times to switch to os-ddclient and have it work with my clients using OPNsense/dyn.com, and several browsing sessions on the forums has not enabled me to come up with a reliable recipe/hack, plus a fear that I'm going to have to migrate everyone to another service, in a hurry, when os-dyndns finally joins IE 11 in the bitbucket.
Dyn.com has support instructions for ddclient at https://help.dyn.com/ddclient/ (https://help.dyn.com/ddclient/), but my I'm really not into leaving my clients with invisible hacks that nobody but me can support in an emergency. Also I don't know how to persist this through upgrades, etc. Finally, the "issues to be aware of" section of those instructions fairly drip with unbillable time.
Any suggestions welcome (including alternate dynamic DNS services with good records, and decent management interfaces for 30 or so names)!
-
after repeated attempts over a number of years, and being stuck between the rock of os-ddclient and the hard place of finding a suitable replacement for dyn.com, I was able, with the timely suggestion of 9axqe to see that my years-old very strong password for all 16 of my clients that need dynamicDNS was the source of the problem.
If you are using os-ddclient, especially with dyndns.com, then I suggest you avoid spaces and @ symbols in your password.
Now, if only dyn.com would allow a per-host password, instead of insisting on one password for all (up to 30) hosts on the account.