ddns with IPv4 and IPv6 #7278
Labels
Milestone
Comments
|
Good day Holder! You mean to update both, IPv4 + IPv6 (if possible)? Makes sense: "IPv6and4". We could then do the IPv4 request first, and allow the IPv6 request afterwards to fail, if either the system does not even have an IPv6 address, or the DDNS server is not reachable via IPv6, or it does not accept to add an IPv6 address to the DNS entry. |
|
Hi Micha, Yes. This is exactly what I mean. Update v4 and afterwards v6 with the option to fail. Sounds great, Holger |
MichaIng
added a commit
that referenced
this issue
Dec 15, 2024
- DietPi-DDNS | The "IPv6or4" option to update IPv6 only, if supported by server, network and provider, has been replaced with "IPv4and6". A server being reachable via IPv6 only is rarely wanted, as many networks do not support it. Instead, usually one will want to have it reachable via both, IPv4 as well as IPv6, which is now possible when using DietPi-DDNS, and the new default. When selected, the IPv4 update needs to succeed to proceed and install the cron job, while the IPv6 update is allowed to fail. In the logs, it will however produce a warning, so admins can check back and in case select IPv4 only, if IPv6 is not supported by server, network or provider. If, e.g. for security reason, IPv6 only is wanted, this option of course remains available, like before. Many thanks to @LOGIN-TB for doing this suggestion: #7278
MichaIng
added
Testing/testers required 🔽
Solution available 🥂
MichaIng
added a commit
that referenced
this issue
Dec 15, 2024
- DietPi-DDNS | The "IPv6or4" option to update IPv6 only, if supported by server, network and provider, has been replaced with "IPv4and6". A server being reachable via IPv6 only is rarely wanted, as many networks do not support it. Instead, usually one will want to have it reachable via both, IPv4 as well as IPv6, which is now possible when using DietPi-DDNS, and the new default. When selected, the IPv4 update needs to succeed to proceed and install the cron job, while the IPv6 update is allowed to fail. In the logs, it will however produce a warning, so admins can check back and in case select IPv4 only, if IPv6 is not supported by server, network or provider. If, e.g. for security reason, IPv6 only is wanted, this option of course remains available, like before. Many thanks to @LOGIN-TB for doing this suggestion: #7278
MichaIng
added a commit
that referenced
this issue
Dec 15, 2024
- DietPi-DDNS | The "IPv6or4" option to update IPv6 only, if supported by server, network and provider, has been replaced with "IPv4and6". A server being reachable via IPv6 only is rarely wanted, as many networks do not support it. Instead, usually one will want to have it reachable via both, IPv4 as well as IPv6, which is now possible when using DietPi-DDNS, and the new default. If, e.g. for security reason, IPv6 only is wanted, this option of course remains available, like before. Many thanks to @LOGIN-TB for doing this suggestion: #7278 - DietPi-DDNS | The cron job does now log server response messages and connection errors separately with respective severities. Some DDNS providers do not return an HTTP error code, but an error text embedded into a regular HTTP 200 response. This, as well as success responses can now be seen via "journalctl -t dietpi-ddns". Many thanks to @jtmoon79 for doing this suggestion: #5954
|
I implemented it just now: #7309 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a feature request
in DDNS Config Menue (dietpi-ddns) we have 3 Options:
IPv4 : Force IPv4 usage for the DDNS update (best compatibility)
IPv6or4 : Do not force any IP family for the DDNS update
IPv6 : Force IPv6 usage for the DDNS update (for modern clients)
It would be great to have the option to activate both protocols for ddns!
Is your feature request related to a problem? Please describe:
In these times it is very helpful if the hosted Servers are available through IPv4 and IPv6
Describe the solution you'd like:
Maybe its helpful to have a 4th option with IPv4 and IPv6 and a fallback to IPv4 if IPv6 is not available
Describe alternatives you've considered:
n/a
Additional context
n/a
Please consider to implement this feature.
Thanks
Holger
The text was updated successfully, but these errors were encountered: