Improved formatting of manage-dns-in-your-network.mdx (#351)

This commit is contained in:
Hammy Havoc
2025-05-29 00:34:35 +02:00
committed by GitHub
parent 82a3c2bcb6
commit b7e90e2334
@@ -41,7 +41,7 @@ For specific cases, you may want to deploy a split horizon configuration for pri
Match domains allow you to route queries to specific nameservers, which is useful for internal DNS configurations Match domains allow you to route queries to specific nameservers, which is useful for internal DNS configurations
that only internal servers can resolve. that only internal servers can resolve.
<Note> <Note>
Only MacOS, Windows 10+, and Linux running `systemd-resolved` support nameservers with match domains. Only macOS, Windows 10+, and Linux running `systemd-resolved` support nameservers with match domains.
For a better experience, we recommend setting at least one nameserver group without match domains to be applied to the `All` group. For a better experience, we recommend setting at least one nameserver group without match domains to be applied to the `All` group.
</Note> </Note>
#### Mark match domains as search domains #### Mark match domains as search domains
@@ -78,7 +78,7 @@ If you choose a predefined public nameserver option, you can select the followin
</p> </p>
After selecting one of the three options, you need to assign a peer group for which this nameserver will be effective. After selecting one of the three options, you need to assign a peer group for which this nameserver will be effective.
In the example below, we chose the "All" group: In the example below, we chose the `All` group:
<p> <p>
<img src="/docs-static/img/how-to-guides/netbird-nameserver-all-group.png" alt="high-level-dia" className="imagewrapper"/> <img src="/docs-static/img/how-to-guides/netbird-nameserver-all-group.png" alt="high-level-dia" className="imagewrapper"/>
</p> </p>
@@ -105,7 +105,7 @@ Below you can see the same nameserver setup but only for the `berlinoffice.com`
</p> </p>
<Note> <Note>
Only MacOS, Windows 10+, and Linux running `systemd-resolved` support nameservers with only match domains. For a better experience, we recommend setting at least a nameserver group without match domains to be applied to the `All` group. Only macOS, Windows 10+, and Linux running `systemd-resolved` support nameservers with only match domains. For a better experience, we recommend setting at least a nameserver group without match domains to be applied to the `All` group.
</Note> </Note>
### Distributing DNS settings with groups ### Distributing DNS settings with groups
@@ -131,7 +131,7 @@ Unfortunately, tools like `nslookup` or `dig` didn't get updated to match these
they won't use the same servers as your browser to query domain names. they won't use the same servers as your browser to query domain names.
For these cases, we listed some tools to support your checks: For these cases, we listed some tools to support your checks:
#### MacOS #### macOS
You can use `dscacheutil`: You can use `dscacheutil`:
```shell ```shell
dscacheutil -q host -a name peer-a.netbird.cloud dscacheutil -q host -a name peer-a.netbird.cloud