Feature #14437
openAdd DynDNS Provider - Hetzner
0%
Description
please add hetzner as a dyndns provider because hetzner does not officially support dyndns, you would have to do it via the dns api https://dns.hetzner.com/api-docs
Updated by Marvin Hörr over 2 years ago
PR: https://github.com/pfsense/pfsense/pull/4714
Old PR: https://github.com/pfsense/pfsense/pull/4654
I messed up my repository and had to create a new one
Updated by Jim Pingle about 2 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.8.0
- Plus Target Version set to 24.07
Updated by Jim Pingle about 2 years ago
- Plus Target Version changed from 24.07 to 24.08
Updated by Jim Pingle over 1 year ago
- Plus Target Version changed from 24.08 to 24.11
Updated by Jim Pingle over 1 year ago
- Plus Target Version changed from 24.11 to 25.01
Updated by Jim Pingle over 1 year ago
- Plus Target Version changed from 25.01 to 25.03
Updated by Jim Pingle over 1 year ago
- Plus Target Version changed from 25.03 to 25.07
Updated by Jim Pingle about 1 year ago
- Target version changed from 2.8.0 to 2.9.0
Updated by Jim Pingle 12 months ago
- Plus Target Version changed from 25.07 to 25.11
Updated by Jim Pingle 7 months ago
- Plus Target Version changed from 25.11 to 26.03
Updated by Jim Pingle 4 months ago
- Plus Target Version changed from 26.03 to 26.07
Updated by Jim Pingle 4 days ago
- Plus Target Version changed from 26.07 to 26.11
Updated by Lennart dV 4 days ago
It's been over two years, what is happening?
Is the target version moved automatically every few months?
Hetzner has moved from the dedicated DNS module, to making it part of the console, with a new endpoint.
I have stopped using PfSense at home, where I used this patch, but others are probably still using it.
Updated by Jim Pingle 4 days ago
The PR is still marked "changes requested" and has conflicts.
Generally speaking, if an issue hasn't been addressed by the time we cut off changes for a given release, we move the target ahead if it isn't critical.
Specifically for this, unless a developer is already using a given service, we can't possibly sign up for and implement every possible Dynamic DNS provider, so we rely on outside submissions for third party services.
Updated by Lennart dV 4 days ago
I am sorry I misinterpreted the origin of the hold-up.