DOCS: lots of broken links

[imlonghao]

Describe the bug

Today I noticed #3430 fix a broken link in docs, so I found a program markdown-link-check in order to find all the broken links in docs. Here is the result of ./documentation/.

There are also GitHub Actions github-action-markdown-link-check and action-linkspector, maybe we can add one of those to verify docs links changed in PRP.

To Reproduce

1. Go to docs
2. Click the specific links
3. Error

Expected behavior

1. Go to docs
2. Click the specific links
3. OK

DNS Provider

• N/A

Additional context

I manually checked some of them due to no action needed, just FYI.

• byo-secrets.md

  • https://github.com/StackExchange/dnscontrol/settings/secrets/actions → Status: 404
  • https://github.com/StackExchange/dnscontrol/settings/variables/actions → Status: 404

• ci-cd-gitlab.md

  • https://gitlab.com/cafferata/dnscontrol/-/pipelines/new → Status: 404

• language-reference/domain-modifiers/AKAMAICDN.md

  • https://blogs.akamai.com/2019/08/fast-dns-zone-apex-mapping-dnssec.html → Status: 0

• language-reference/domain-modifiers/AZURE_ALIAS.md

  • https://resources.azure.com/ → Status: 401

• language-reference/domain-modifiers/CF_REDIRECT.md

  • ../provider/cloudflareapi.md → Status: 400

• language-reference/domain-modifiers/CF_TEMP_REDIRECT.md

  • ../provider/cloudflareapi.md → Status: 400

• language-reference/domain-modifiers/PTR.md

  • ../global/D_EXTEND.md → Status: 400

• language-reference/top-level-functions/REV.md

  • ../domain/PTR.md → Status: 400

• opinions.md

  • #opinion-3-dnsconfig.js-are-not-zonefiles → Status: 404

• provider/akamaiedgedns.md

  • https://www.akamai.com/products/edge-dns → Status: 0
  • https://techdocs.akamai.com/edge-dns/reference/edge-dns-api → Status: 0
  • https://www.akamai.com/developer → Status: 0
  • https://www.akamai.com/blog/security/edge-dns--zone-apex-mapping---dnssec → Status: 0

• provider/cloudflareapi.md

  • https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys → Status: 403

• provider/easyname.md

  • https://my.easyname.com/en/account/api → Status: 401

• provider/hetzner.md

  • https://dns.hetzner.com/settings/api-token → Status: 429

• provider/index.md

  • language-reference/domain-modifiers/ALIAS.md → Status: 400
  • language-reference/domain-modifiers/CAA.md → Status: 400
  • language-reference/domain-modifiers/AUTODNSSEC_ON.md → Status: 400
  • language-reference/domain-modifiers/HTTPS.md → Status: 400
  • language-reference/domain-modifiers/LOC.md → Status: 400
  • language-reference/domain-modifiers/NAPTR.md → Status: 400
  • language-reference/domain-modifiers/PTR.md → Status: 400
  • language-reference/domain-modifiers/SOA.md → Status: 400
  • language-reference/domain-modifiers/SRV.md → Status: 400
  • language-reference/domain-modifiers/SSHFP.md → Status: 400
  • language-reference/domain-modifiers/SVCB.md → Status: 400
  • language-reference/domain-modifiers/TLSA.md → Status: 400
  • language-reference/domain-modifiers/DS.md → Status: 400
  • language-reference/domain-modifiers/DHCID.md → Status: 400
  • language-reference/domain-modifiers/DNAME.md → Status: 400
  • language-reference/domain-modifiers/DNSKEY.md → Status: 400
  • provider/azure_dns.md → Status: 400
  • provider/bind.md → Status: 400
  • provider/cloudflareapi.md → Status: 400
  • provider/cscglobal.md → Status: 400
  • provider/gcloud.md → Status: 400
  • provider/msdns.md → Status: 400
  • provider/route53.md → Status: 400
  • provider/azure_private_dns.md → Status: 400
  • provider/akamaiedgedns.md → Status: 400
  • provider/axfrddns.md → Status: 400
  • provider/bunny_dns.md → Status: 400
  • provider/cloudns.md → Status: 400
  • provider/cnr.md → Status: 400
  • provider/desec.md → Status: 400
  • provider/digitalocean.md → Status: 400
  • provider/dnsimple.md → Status: 400
  • provider/dnsmadeeasy.md → Status: 400
  • provider/dnsoverhttps.md → Status: 400
  • provider/domainnameshop.md → Status: 400
  • provider/easyname.md → Status: 400
  • provider/exoscale.md → Status: 400
  • provider/gandi_v5.md → Status: 400
  • provider/gcore.md → Status: 400
  • provider/hedns.md → Status: 400
  • provider/hetzner.md → Status: 400
  • provider/hexonet.md → Status: 400
  • provider/hostingde.md → Status: 400
  • provider/huaweicloud.md → Status: 400
  • provider/internetbs.md → Status: 400
  • provider/inwx.md → Status: 400
  • provider/linode.md → Status: 400
  • provider/loopia.md → Status: 400
  • provider/luadns.md → Status: 400
  • provider/namecheap.md → Status: 400
  • provider/netcup.md → Status: 400
  • provider/netlify.md → Status: 400
  • provider/ns1.md → Status: 400
  • provider/opensrs.md → Status: 400
  • provider/oracle.md → Status: 400
  • provider/ovh.md → Status: 400
  • provider/packetframe.md → Status: 400
  • provider/powerdns.md → Status: 400
  • provider/realtimeregister.md → Status: 400
  • provider/rwth.md → Status: 400
  • provider/sakuracloud.md → Status: 400
  • provider/softlayer.md → Status: 400
  • provider/transip.md → Status: 400
  • provider/vultr.md → Status: 400
  • bug-triage.md → Status: 400

• provider/linode.md

  • https://www.linode.com/docs/api/domains/#domains-list__responses → Status: 403

• provider/namedotcom.md

  • https://www.name.com/reseller/apply → Status: 404

• provider/route53.md

  • https://aws.amazon.com/developers/access-keys/ → Status: 404

• provider/rwth.md

  • https://noc-portal.rz.rwth-aachen.de/dns-admin/en/api_tokens → Status: 0

• release-engineering.md

  • https://github.com/StackExchange/dnscontrol/settings/variables/actions → Status: 404
  • https://github.com/StackExchange/dnscontrol/settings/secrets/actions → Status: 404

[cafferata]

There are also GitHub Actions github-action-markdown-link-check and action-linkspector, maybe we can add one of those to verify docs links changed in PRP.

Good idea! I’ve prepared a proof of concept in GitHub pull request #3439.