Yes, but there's already scripts handling many of the most popular.
Check out acme.sh and remember, changing your DNS provider or hosting it yourself really isn't that bad.
Check out acme.sh and remember, changing your DNS provider or hosting it yourself really isn't that bad.
So my suspicion seems accurate. The script will need to know how to interface with each provider and you (as an end user) will also need to be responsible for setting up your own API keys for whatever provider you use.
$ foo mydomain.org --init ovh
$ foo mydomain.org my.sub A 1.2.3.4
$ foo mydomain.org my.sub AAAA 1234::abcd
$ foo mydomain.org --remove my.sub A [1.2.3.4]
I have yet to find anything that handles any DNS changes in a simple, stupid way. Most API clients I've seen only handle one kind of request: acme.sh only does TXT challenges. DynDNS endpoint only does A records. Etc.
If this is something you need to do a regular basis, you might consider hosting your own DNS and using BIND's nsupdate tool.
meh. There are some things that I'd gladly host, but DNS clerly isn't among them. Too many ways to screw up, probable breakage ahead (only 1 dedicated @ OVH), so many rate-limits to implement; DNS servers a re filled with RCEs... (bind being the worst).
Clearly, nope. Not doing this ;)