pfSense

Jim Pingle wrote in #note-2:

Whatever service that is, it would need to be added as a supported provider and not be handled via the custom option. Not every provider can be accommodated that way since many require custom API calls, keys, etc.

You'll need to post the provider name and a pointer to its documentation on how to implement a dynamic DNS client and then maybe it can be added as a supported provider.

Hi Jim,

That is the Dyn.com Dynamic DNS service as indicated in my screenshots. If I'm not mistaken the oldest and first such service ever listed in pfsense. The screenshot in this ticket description is the key feature available in the dyn.com portal. The second screenshot I posted is the selection in the pfsense service drop-down in which there are three DynDNS entries available, all of which are missing a key option.

Regards,
Matt

Dyn Update clients - https://help.dyn.com/update-clients/

Dyn.com portal https://account.dyn.com/

It wasn't clear except for one tiny spot on one screenshot that you meant "dyn.com", "DynDNS" is a generic term and wasn't specific enough there.

The current implementation of those "DynDNS (dynamic/custom/static)" entries is all tied to their old "dyndns.org" setup and not "dyn.com" -- There are no references to "dyn.com" in the current repository.

If they changed their supported update methods or procedures it would still need to be treated as a new provider since it would require a new client setup (or completely rewriting the current ones) to tie into their new API.

Hi Jim,

If I'm not mistaken it is the same service, just under a different domain name. Dyn was acquired by Oracle some time ago. I'm just the end user / admin here and not affiliated with them other than having an account for years.

Regards,
Matt

Matt Keys wrote in #note-6:

If I'm not mistaken it is the same service, just under a different domain name. Dyn was acquired by Oracle some time ago. I'm just the end user / admin here and not affiliated with them other than having an account for years.

Yes that appears to be the case but what I'm saying is the backend code is all referencing the old name so if they changed the API and update methods it's still a "new" client even if they just renamed the service.

If we rename/change the existing entries it may break current clients who can still use the old setup, unless they have shut all that down (which, if they had, I'd expect to see more people mentioning)

They have not shut down username password auth as mine is still operating. They have just added key auth. The reason being (as noted in the screeshot) if you have the username / password, you have TLD admin for whatever the domain is you're trying to update. Key auth was added to provide means to update without giving away TLD root. dyndns appears to still be the destination domain despite the dyn.com change, see https://oci.dyn.com/dynamic-dns-hostname-search/

OK so all of that still points toward it needing a new client entry created so it needs to be treated as such. Please start a fresh issue with the pointers to their new key-based auth info. No need for the screenshots, just the links for the API/key info/client info and noting that it needs to be a new client for Dyn.com key-based auth.

Jim Pingle wrote in #note-9:

OK so all of that still points toward it needing a new client entry created so it needs to be treated as such. Please start a fresh issue with the pointers to their new key-based auth info. No need for the screenshots, just the links for the API/key info/client info and noting that it needs to be a new client for Dyn.com key-based auth.

https://redmine.pfsense.org/issues/15213