fiwswe

How about separating the potential FRITZ!OS issues from the actual deSEC update mechanism? Build the test URL manually and send it via e.g. curl. E.g. use these two URLs alternately...

I have built a testing setup for the FRITZ!OS DynDNS client as follows: * A webserver (hosted outside of my LAN) that always returns HTTP status 200 and `good` for...

@renne Initially I didn't but I just checked now: * The input field _Domainnamen:_ does not accept a comma separated list. This is just a UI issue though. * I...

@peterthomassen The only drawback I can see with your approach is that using the `myipv4` and `myipv6` qualifiers may require the additional hostname(s) to be duplicated if both IPv4 and...

Just to clarify your testing request: You want to make sure that the URL syntax `keyword:host=value` would work on FRITZ!OS, correct? I.e. that a URL parameter name containing a `:`...

Sorry, I found no way to change the commit message of the [first commit](https://github.com/desec-io/desec-stack/pull/1170/commits/7d114e54d1e5fff20439e10ed151ed6266d59d2b). If needed I'll withdraw the PR and create a new one. Please let me know.

Not really as I am only using the GitHub web interface. And it does not offer this option. Also from what I understand the `--amend` option can potentially cause issues....