ci: add check-docs workflow (#93)

* ci: add check-docs workflow

* chore: ignore node_modules

* chore(deps): add package-lock

* style: apply formatting

* style: apply formatting

* fix: fix typo

* fix: fix all proposed changes by markdown-lint

* fix: fix trailing spaces

* fix(troubleshooting.md): apply minor fi

* fix(getting-started): apply minior fix

* ci: dont' kick off build when changes made to check-doc.yml

* ci: ONLY kick off build when target workflow file changes

* trigger build

* fix(build.yml): fix syntax

* trigger build

* fix: fix broken syntax
This commit is contained in:
Kevin Yu
2023-05-21 00:41:44 +08:00
committed by GitHub
parent ae6667bb5d
commit eac04e991b
24 changed files with 10005 additions and 90 deletions

View File

@ -7,7 +7,7 @@ If you use a external DNS like AdguardHome, you could refer to the following gui
## External DNS on localhost
If you set up an external DNS on localhost, you may want to let the DNS queries to dns.google.com proxied. For example, if you have the following configuration in AdguardHome:
If you set up an external DNS on localhost, you may want to let the DNS queries to `dns.google.com` proxied. For example, if you have the following configuration in AdguardHome:
```
Listen on: the same machine with dae, port 53.
@ -53,7 +53,7 @@ You should configure dae as follows:
## External DNS on another machine in LAN
If you set up a external DNS on another machine in LAN, you may want to let the DNS queries to dns.google.com proxied. For example, if you have following configuration in AdguardHome:
If you set up a external DNS on another machine in LAN, you may want to let the DNS queries to `dns.google.com` proxied. For example, if you have following configuration in `AdguardHome`:
```
Listen on: 192.168.30.3:53 (mac address: 8c:16:45:36:1c:5a)
@ -73,9 +73,9 @@ You should configure dae as follows:
# Or use MAC address if in the same link:
# mac(8c:16:45:36:1c:5a) && l4proto(udp) && dport(53) -> must_direct
```
And make sure domain `dns.google.com` will be proxied in routing rules.
3. Add upstream and request to section "dns".
```