diff options
| author | Benjamin Franzke <benjaminfranzke@googlemail.com> | 2022-05-17 15:54:46 +0200 |
|---|---|---|
| committer | Benjamin Franzke <benjaminfranzke@googlemail.com> | 2022-05-17 23:00:18 +0200 |
| commit | 818e46ae7c3159ef3026930c1a4330f66344b2d1 (patch) | |
| tree | 417aaf5acf0f2ba950df2e719c07ff8ca7927ecb /docs/RESOLVED-VPNS.md | |
| parent | 85b5930b7b3c2099f450438ab02260b41cb3bef3 (diff) | |
| download | systemd-818e46ae7c3159ef3026930c1a4330f66344b2d1.tar.gz | |
docs: avoid multiple first-level headlines
One document should only contain one main
headline, both for structuring and for
visual reasons.
Relevant cases found via:
git grep -A2 '^# ' docs/
Diffstat (limited to 'docs/RESOLVED-VPNS.md')
| -rw-r--r-- | docs/RESOLVED-VPNS.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/RESOLVED-VPNS.md b/docs/RESOLVED-VPNS.md index e06fbc3d2f..97c1125242 100644 --- a/docs/RESOLVED-VPNS.md +++ b/docs/RESOLVED-VPNS.md @@ -112,7 +112,7 @@ and another one with `~corp.company.example` — both suffixes match a lookup fo `foo.corp.company.example`, but the latter interface wins, since the match is for four labels, while the other is for zero labels. -# Putting it Together +## Putting it Together Let's discuss how the three DNS routing concepts above are best used for a reasonably complex scenario consisting of: @@ -159,7 +159,7 @@ else. If `privacy0` is then downed again, `wifi0` will get the regular DNS traffic again, and `company0` will still get the company's internal domain and IP subnet traffic and nothing else. Everything hence works as intended. -# How to Implement this in Your VPN Software +## How to Implement this in Your VPN Software Most likely you want to expose a boolean in some way that declares whether a specific VPN is of the *corporate* or the *privacy* kind: @@ -177,7 +177,7 @@ specific VPN is of the *corporate* or the *privacy* kind: traditional, i.e. with any search domains as acquired, do not set `~.` though, and do not disable `default-route`.) -# The APIs +## The APIs Now we determined how we want to configure things, but how do you actually get the configuration to `systemd-resolved.service`? There are three relevant @@ -222,7 +222,7 @@ interfaces: propagate the `default-route` boolean, nor can be used to configure the `~….in-addr.arpa` or `~.ip6.arpa` routing domains. -# Ordering +## Ordering When configuring per-interface DNS configuration settings it is wise to configure everything *before* actually upping the interface. Once the interface @@ -235,7 +235,7 @@ as the former without the latter has no effect, but the latter without the former will result in DNS traffic possibly being generated, in a non-desirable way given that the routing information is not set yet. -# Downgrading Search Domains to Routing Domains +## Downgrading Search Domains to Routing Domains Many VPN implementations provide a way how VPN servers can inform VPN clients about search domains to use. In some cases it might make sense to install those |