Skip to content

os-ddclient: OPNsense backend - custom dyndns2 endpoint #3362

Description

@ei-ke

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

Is your feature request related to a problem? Please describe.
Current state: The OPNsense backend that has been added to os-ddclient allows to choose the interface and also to only use the interface's IPv6 address for the available dyndns providers. This, in theory, solves the issue with CGNAT that I described a while back (#2872) where the CGNAT IPv4 and the public IPv6 is pushed to the dyndns provider when using the ddclient backend.
A workaround was using external services that just reply the IPv6 address to ddclient. But sometimes I got timeouts and honestly prefer to do those things locally.

Describe the solution you'd like
As written here I'd like to suggest to offer a generic dyndns2 option like the "Custom" service option when using the ddclient backend where I can just enter the dyndns server I'm using - btw: it's desec.io .

Describe alternatives you've considered
The other option would be to port the interface chek IP method with the IPv4/IPv6 option for the ddclient backend which already has the "Custom" service option. Not sure which is easier to implement / maintain.

Additional context

Metadata

Metadata

Assignees

Labels

featureAdding new functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions