Add info about the dns_myloc API interface

dnsapi2.md

@@ -87,6 +87,7 @@
 - [163. Use hosttech API](#dns_hosttech)
 - [164. Use Alviy API](#dns_alviy)
 - [165. Use Timeweb Cloud DNS API](#dns_timeweb)
+- [165. Use myLoc.de / webtropia.com DNS API](#dns_myloc)
 - [Use custom API](#dns_myapi)
 - [Use lexicon DNS API](#dns_lexicon)
 
@@ -2163,6 +2164,29 @@ Finally, сonsider the following command as an example of how to issue a certifi
 
 Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/5140).
 
+<a name="dns_myloc"/>
+
+## 166. Use myLoc.de / webtropia.com DNS API
+
+First, you need a domain hosted at myLoc.de or webtropia.com. A Webtropia also allows to use the myloc.de API.
+You need to register a token via the [myLoc.de website](https://zkm.myloc.de/s/api/token) or the [Webtropia.com website](https://zkm.webtropia.com/s/api/token).
+
+As the API does not allow to match domain names to zones yet, the zone has to be set manually if you plan to use subdomains.
+You can set the zone as well as the token using environment variables:
+```sh
+export MYLOC_token=aabbccddeeffgghhiijjkkllmmnnjjkkllmmnnooppqqrrsstt
+export MYLOC_zone=example.com
+```
+If `MYLOC_zone` is not set, it will be guessed by stripping the `_acme-challenge.` prefix from the domains being processed.
+This may not match the zone, for example for issueing certificates for `sub1.example.com`, the zone probably is `example.com`.
+
+Now, use the dns_myloc backend to issue and renew certificates using DNS-01:
+```sh
+./acme.sh --issue --dns dns_myloc -d example.com,*.example.com,foo.bar.example.com
+```
+
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/5193).
+
 <a name="dns_myapi"/>
 
 ## Use custom API
@@ -2183,7 +2207,6 @@ For more details, please check our sample script: [dns_myapi.sh](https://github.
 
 See: [DNS API Dev Guide](https://github.com/acmesh-official/acme.sh/wiki/DNS-API-Dev-Guide)
 
-
 <a name="dns_lexicon"/>
 
 ## Use lexicon DNS API