dns/ddclient: supporting IPv6 prefixes in native backend

[kevinchalet]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.

Some providers - like dynv6.net - support assigning a static IPv6 suffix to a host (e.g ::aaaa:aaaa:aaaa:aaaa) and make the IPv6 prefix dynamically configurable via the API. It's an extremely convenient feature that avoids having to install a DynDNS client on each machine (each having to update its own record).

Describe the solution you'd like

That would be awesome if OPNsense's native ddclient backend supported the ipv6prefix parameter (in this case, I'd assume the prefix would need to be resolved from the selected LAN interface, rather than from an external service).

Here's the docs for dynv6: https://dynv6.com/docs/apis.

Describe alternatives you've considered

N/A

Additional context

https://twitter.com/kevin_chalet/status/1692614974110142682
https://twitter.com/dennis_schroed/status/1692863779569049954

[b1ggi]

would be a great addition

[Tschak77]

good point I vote for this feature too

[fichtner]

I'm not entirely clear if this is a feature request for us (implemented in ddclient) or a feature request for a feature in ddclient (not implemented in ddclient) to be used from our side in which case I'd have to tag this "upstream".

[kevinchalet]

@fichtner I'm not an expert, but I thought the dynamic DNS plugin had a native backend that didn't depend on ddclient (from the docs: "With ddlient developments sunsetting we decided to offer an alternative written in Python"). If such feature was added to the native backend, it wouldn't need to be implemented upstream, right?

[fichtner]

Let me change the subject then. The +1's aren't really helping make this clear. Thanks!

[kevinchalet]

Ah yeah, sorry for the confusion (I guess naming the OPNsense plugin ddclient didn't help 😄)

[fichtner]

True, adding the backend option was a necessity after ddclient went EoL for a while and now it's a bit problematic ;)

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

[kevinchalet]

@fichtner looks like @OPNsense-bot was a bit overzealous on this one as the thread is still quite active. Any chance you could reopen it? 😃

[Commifreak]

+1

What about providers without a direct prefix support? Wouldnt it be a nice idea to support dynamic hosts for address updates? So the dyndns client could send the full, current IP from a dynamic host to cloudflare as an example?

EDIT: I think there are two things: The ip6prefix parameter, to send to supporting providers, and a general option "send only updated prefixes" which "patch" the prefix in the record and leave the inderface identifier as is.