diff --git a/docs/how-to-guides/nameservers.md b/docs/how-to-guides/nameservers.md index 75e3c14c..50e1ea61 100644 --- a/docs/how-to-guides/nameservers.md +++ b/docs/how-to-guides/nameservers.md @@ -107,6 +107,32 @@ Then we need to confirm that an access rule exists to connect `Remote developers high-level-dia

+## Testing configuration +### Querying records +DNS configuration has evolved in the last few years, and each operating system might expose its nameserver configuration differently. Unfortunately, tools like `nslookup` or `dig` didn't get updated to match these OS configurations, and in many cases, 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: +#### MacOS +You can use `dscacheutil`: +```shell +dscacheutil -q host -a name peer-a.netbird.cloud +``` +#### Windows +You can use `Resolve-DnsName` on `Powershell`: +```shell +Resolve-DnsName -Name peer-a.netbird.cloud +``` +#### Linux +In most cases, you will be fine with traditional tools because most DNS managers on Linux tend to update the /etc/resolv.conf. +```shell +dig peer-a.netbird.cloud +# or +nslookup peer-a.netbird.cloud +``` +If your system is running systemd-resolved, you can also use ```resolvectl```: +```shell +resolvectl query peer-a.netbird.cloud +``` ## Get started