3 ms·
If you're up for the task, I've wanted to write a script (POSIX /bin/sh certainly) for interaction with DNS providers. Basically lower the entry barrier, and av
by moviuro 9y ago
If you're up for the task, I've wanted to write a script (POSIX /bin/sh certainly) for interaction with DNS providers. Basically lower the entry barrier, and avoid the web interface:
$ 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]
etc.
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.
- piracykills 9y agoIt'd be cool to have and it's relatively straightforward from a software engineering perspective, but it's so much boring grunt work that finding someone who wants to implement it might be challenging. If this is something you need to do a regular basis, you might consider hosting your own DNS and using BIND's nsupdate tool.
- moviuro 9y ago> hosting your own DNS 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 ;)