diff --git a/src/content/en/pages/knowledgebase/linux/linux-webpages-do-not-load-or-dns-leaks-when-connecting-via-networkmanager.md b/src/content/en/pages/knowledgebase/linux/linux-webpages-do-not-load-or-dns-leaks-when-connecting-via-networkmanager.md index 232bf02c9..126e56d5c 100644 --- a/src/content/en/pages/knowledgebase/linux/linux-webpages-do-not-load-or-dns-leaks-when-connecting-via-networkmanager.md +++ b/src/content/en/pages/knowledgebase/linux/linux-webpages-do-not-load-or-dns-leaks-when-connecting-via-networkmanager.md @@ -12,6 +12,8 @@ weight: 110 When you connect to a VPN server using the NetworkManager, you might discover that it does not apply IVPN DNS IP address automatically. This may lead to either websites' domain names not resolving or your real DNS is being used, which is considered as a leak. +IVPN DNS IP addresses and details are listed [here](/knowledgebase/troubleshooting/what-is-the-ip-address-of-your-dns-servers/). The `198.245.51.147` address referenced below is our public DNS server. Addresses in the private address space, like `10.0.254.x` are internal to the VPN connection. For the internal DNS, feel free to use any from the list, like to activate different levels of the AntiTracker. + If you are more comfortable with NetworkManager, feel free to apply IVPN DNS IP addresses manually: