Sharing my (real) first selfhosted project: OVH IP updater (github.com)
from decisoft@lemm.ee to selfhosted@lemmy.world on 18 Nov 12:35
https://lemm.ee/post/47688252

Hi everyone!

I want this to be my first post here over Lemmy.

Recently, I moved my domains from GoDaddy to OVH due to GD’s policy changes that removes the ability of using its API for updating the IP of subdomains if you don’t pay more or you don’t have more than X domains with them.

When I looked up for methods or APIs to update the IP of my subdomains on OVH, I realised that all the methods that I found uses the the “DynHost” option from OVH, so you need to create another subdomain with credentials, that were the one you will update with your IP, and then associate that with your real A subdomain.

I’m more an API guy, so I made a quick research and found that OVH has also API endpoints that allows to update the IP of the subdomain(s) you want, as I was doing with GoDaddy and other providers.

So I made a real simple IP updater for OVH that uses this method! Feel free to comment, use or share, this is my real first opensource and selfhosted project and I want to learn :)

#selfhosted

threaded - newest

poVoq@slrpnk.net on 18 Nov 16:14 next collapse

Cool. I am currently using the OVH dyndns option and it is a bit annoying that you have to update each sub-domain individually and can’t just tell OVH to update all subdomains to the same new IP via a wildcard.

Is that something your script could do?

Also it seems like the OVH dyndns API currently only does either IPv4 or IPv6 but not both the same time.

Edit: Ah I see you plan to allow creating sub-domains through it. I guess that would indirectly solve my issue as well.

decisoft@lemm.ee on 18 Nov 17:38 collapse

Hi!

Thanks for your feedback. First of all, I’ve just dropped a new update that will create a subdomain if you specify one on the environment variables that does not exist. That was a cool feature I use a lot on previous Docker images I used with other providers.

I don’t know if that solves your problem (I think not), but I will be glad of hearing your issue. I don’t know if you want to put a single * or something like that in the field of subdomains to update, instead of writing all down (sub1, sub2, sub3, sub4, sub5).

Regarding IPv4 and IPv6, I’m working on implement IPv6 now, I want that to be part of the next release (within one month), as well as multi-arch images. Definitely, I will try to update both at the same time as you want.

Thanks again!

Edit: and of course, feel free to open an issue to ask for more features or bug fixes you may face!

poVoq@slrpnk.net on 18 Nov 18:54 collapse

It does solve my problem in the sense that right now I need to configure each subdomain individually both in the OVH web-ui and then a second time on my firewall for the dyndns update. With a few dozen subdomains that is both annoying and easy to mess up accidentally.

If I can manage everything from env parameters in a single location that saves me a lot of hassle.

abeorch@lemmy.ml on 18 Nov 17:47 collapse

Wow this is cool. Do you use OpenWrt at all? It would be amazing to integrate with its DYNDns package.

decisoft@lemm.ee on 18 Nov 17:56 collapse

Yes! I use it and yes, I looked into that package and then realised that it uses DynHost too (I don’t believe that all packages and docker images all around the web uses DynHost and not API).

It’s on my list to learn how to integrate this method into ddns-scripts package of OpenWRT. But I develop this tools on my free time, so there is a lot to do and no time. But I will look into it.

thanks for your comment!