OPNsense Forum

English Forums => General Discussion => Topic started by: Alphakilo on September 07, 2018, 08:12:15 pm

Title: Gandi.net API support for os-dyndns?
Post by: Alphakilo on September 07, 2018, 08:12:15 pm
So. For my homelab I have lots and lots of domains and subdomains. Currently they are registered with Cronon (STRATO).
Since I'm pretty darn tired of STRATOs fits and general backwardness, I'd like to transfer them to a provider that actually knows what they're doing. I've evaluated some providers and settled for gandi.net.

Now comes the complicated part:

I have an dynamic public IP that changes on every reconnect, or at very least on every forced reconnect (24h). The os-dyndns is doing a great job with STRATO, at least as good as it can with that company (yes, I'm salty).

But it seems it has no option for the gandi.net API (https://doc.livedns.gandi.net/).

There's an python implementation over at GitHub (https://github.com/cavebeat/gandi-live-dns), but I'd also like to keep the process of DynDNS updates on the OPNsense. While not potentially compromising my border gateway by running 3rd party stuff on it. CNAME is also not an option.

That leaves me... Well, here. Asking for help ;)

Maybe I'm just not seeing how it can be done?
Maybe it could be implemented?

If the latter is true, welp, my PHP doesn't go far beyond <?php phpinfo(); ?>. But I'd be happy to help by testing and providing API keys.

Cheerio!
Title: Re: Gandi.net API support for os-dyndns?
Post by: jkhii on March 17, 2020, 08:41:17 am
I too would like to see Gandi LiveDNS supported for Dynamic DNS.
Title: Re: Gandi.net API support for os-dyndns?
Post by: bigbrother on May 11, 2021, 08:42:47 pm
Did you find any solution?

Gandi Live DNS is supported but I struggle with the configuration in Opensense.

Username/Password ? What about the APi key?
Title: Re: Gandi.net API support for os-dyndns?
Post by: le_top on July 15, 2023, 12:34:47 am
When looking at the dyndns log, I can see that the password is used as "Authorization: Apikey PASSWORD", so the password should be the Api key.

I ran into difficulties basically because the service I selected to identify my IP address returned an empty result.
After changing the service, the IP update worked properly with an empty username and the Api key as the password.

The hostnames are the "subdomain" - for the root domain one has to set "@".