fiwswe

Very welcome PR! Thanks for your work on this :-) The syntax you chose seems to assume that there will never be TLDs with the names `ip`, `ipv6`, `myip`, `myipv4`...

@peterthomassen Thinking about it, I agree that the suffix is unnecessary. That would also help to keep down the length of the URL. Even the scenario where one would want...

@molikuner Thanks for your work! Any API where the same parameter can be used multiple times (possibly relying on the order of parameters) is probably not a good idea. That...

About the potential ambiguity with the potential future TLD `ip.`: This could be resolved by optionally allowing FQDNs instead of hostnames without the trailing `.`. The parameter name `ip=` is...

> This is already how the existing query parameters work. If you specify them multiple times, only the last one will be considered. Are you referring to URL parameters in...

@nils-wisiol No, I don't think anything we are trying to change in this PR is a feature not supported by the general API. (Let's turn that statement around: I think...

> With non-suffixed domain parameters one would have to create the following request: > > ``` > ?hostname=example.com,ipv4.example.com,ipv6.example.com > &myipv4=1.2.3.4 > &myipv6=2001:db8::1 > &ipv6.example.com=2001:db8::1, > &ipv4.example.com=1.2.3.4, > ``` I disagree....

Oops sorry, I just noticed (after sending of course) that my alternatives do not handle removing the `A` RRset for `ipv6.example.com`. They keep it unchanged (if it exists). Correcting that...

So is avoiding the need to use an IP/prefix more than once a required goal here? For DDNS clients the only one I know, where using a placeholder more than...

@renne > Do I understand correctly it is possible since the merge of https://github.com/desec-io/desec-stack/pull/1112 to use multiple subdomains in a comma-separated list but not to overwrite IPv6 addresses with the...