diff --git a/dnsapi.md b/dnsapi.md
index fea87e60..059a2470 100644
--- a/dnsapi.md
+++ b/dnsapi.md
@@ -1,8 +1,6 @@
 # How to use DNS API
 
-If your DNS provider doesn't provide API access, you can use our DNS alias mode:
-
-https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode
+If your DNS provider doesn't provide API access, you can use our [DNS alias mode](https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode)
 
 
 * [1. CloudFlare](#dns_cf)
@@ -179,7 +177,7 @@ export CF_Account_ID="<id>"
 In order to use the new token, the token currently needs access read access to Zone.Zone, and write access to Zone.DNS, across all Zones.
 See [Issue #2398](https://github.com/acmesh-official/acme.sh/issues/2398) for more info.
 
-Alternatively, if the certificate only covers a single zone, you can restrict the API Token only for write access 
+Alternatively, if the certificate only covers a single zone, you can restrict the API Token only for write access
 to Zone.DNS for a single domain, and then specify the `CF_Zone_ID` directly:
 
 ```sh
@@ -1315,7 +1313,7 @@ The `NC_Apikey`,`NC_Apipw` and `NC_CID` will be saved in `~/.acme.sh/account.con
 
 ## 53. Use Namecheap
 
-You will need your namecheap username, API KEY (https://www.namecheap.com/support/api/intro.aspx) and your 
+You will need your namecheap username, API KEY (https://www.namecheap.com/support/api/intro.aspx) and your
 external IP address (or a URL to get it), this IP will need to be whitelisted at Namecheap.
 Due to Namecheap's API limitation all the records of your domain will be read and re applied,
 make sure to have a backup of your records you could apply if any issue would arise.
@@ -1384,6 +1382,8 @@ Ok, let's issue a cert now:
 
 The hosting.de API key and endpoint will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2058)
+
 
 <a name="dns_neodigit" />
 
@@ -1438,6 +1438,8 @@ You can then issue certs by using:
 ./acme.sh --issue --dns dns_pointhq -d example.com -d www.example.com
 ```
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2060)
+
 
 <a name="dns_active24" />
 
@@ -1458,6 +1460,8 @@ Now, let's issue a cert, set `dnssleep` for propagation new DNS record:
 
 The `ACTIVE24_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2059)
+
 
 <a name="dns_doapi" />
 
@@ -1477,6 +1481,8 @@ To issue a certificate run:
 
 The API token will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2057)
+
 
 <a name="dns_nw" />
 
@@ -1523,6 +1529,8 @@ Finally, we'll issue the certificate: (Thermo DNS publishes at max every 15 minu
 
 The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2088)
+
 
 <a name="dns_nw" />
 
@@ -1545,6 +1553,8 @@ Finally, we'll issue the certificate: (Futurehosting DNS publishes at max every
 
 The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2088)
+
 
 <a name="dns_rackspace" />
 
@@ -1597,7 +1607,7 @@ Make sure that you can execute own binaries:
 devil binexec on
 ```
 
-Install acme.sh, or simply `git clone` it into some directory on your MyDevil host account 
+Install acme.sh, or simply `git clone` it into some directory on your MyDevil host account
 (in which case you should link to it from your `~/bin` directory).
 
 If you're not using private IP and depend on default IP provided by host, you may want to edit `crontab` too,
@@ -1611,6 +1621,8 @@ To issue a new certificate, run:
 
 After certificate is ready, you can install it with [deploy command](https://github.com/acmesh-official/acme.sh/wiki/deployhooks#14-deploy-your-cert-on-mydevilnet).
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2079)
+
 
 <a name="dns_cn" />
 
@@ -1672,7 +1684,6 @@ To issue a cert run:
 
 `ZONE_Username` and `ZONE_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-
 Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2146)
 
 
@@ -1701,6 +1712,8 @@ To issue a cert run:
 
 `ULTRA_USR` and `ULTRA_PWD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2118)
+
 
 <a name="dns_desec" />
 
@@ -1778,9 +1791,11 @@ Use [dnsConsole](https://dns.hetzner.com/) to create your hetzner api token.
 Issuing a certificate (using LetsEncrypt):
 ```sh
 export HETZNER_Token="<token>" 
-./acme.sh --issue --dns dns_hetzner -d example.com -d  www.example.com --server letsencrypt
+./acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com --server letsencrypt
 ```
 
+Report any bugs or issues [here](https://github.com/acmesh-official/acme.sh/issues/2943)
+
 
 <a name="dns_ddnss" />