ddclient: Mismatched protocols, no server override for `nsupdatev4` and `nsupdatev6` account types

[arichtman]

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.

I am attempting to configure DDclient to use nsupdate against OPNsense's Bind service.
To do this I need to have DDclient use protocol type nsupdate with the server configured to localhost and the Bind port.
It appears however that nsupdate account types:

• Set the protocol to dyndns2 - which is distinctly not the DDclient protocol official documentation here
• Hard-codes the server address with no override option source here

Describe the solution you'd like

When I select an account type of nsupdatev6 I would like nsupdate to be the configured protocol.
A GUI text option for overriding any default server configuration.

Describe alternatives you've considered

A hook script to modify the generated configuration.

Additional context

[arichtman]

Ah, I see we're moving away from ddclient backend. I had a rummage about the new native backend Python files and didn't see anything that suggested nsupdate support - is this then a new feature request?

[fichtner]

Hi @arichtman,

Historically, dns/rfc2136 was always the one to use nsupdate. Ddclient upstream looks dead again after a brief revival period.

Scope matters WRT rfc2136 plugin can be used or should be replaced by a native dyndns backend.

Cheers,
Franco

[arichtman]

Good point, I would lean towards native dyndns backend as it obviates the need for the rfc2136 plugin.

Also I can see rfc2136 plugin:

• Doesn't take a file path for key, so integrates a little more poorly with BIND9 (related os-bind: RNDC key file separation #5106 )
• Warns You must configure a DNS server [...] or allow the DNS server list to be overridden by DHCP/PPP on WAN for dynamic DNS updates to work. - which means having to change other configuration

[fichtner]

Although these things could be changed in the RFC2136 plugin I don't disagree with your assessment as it's very old and takes work to move to MVC, but then we'd want a native binding and avoid ddclient as it will be removed sooner or later anyway given it's recent failure to be maintained (again).

Cheers,
Franco