diff --git a/docs/private-dns/api/_category_.json b/docs/private-dns/api/_category_.json index ebc3a0c43..88db94c3e 100644 --- a/docs/private-dns/api/_category_.json +++ b/docs/private-dns/api/_category_.json @@ -1,5 +1,5 @@ { - "position": 2, + "position": 6, "label": "API", "collapsible": true, "collapsed": true diff --git a/docs/private-dns/connect-devices/_category_.json b/docs/private-dns/connect-devices/_category_.json new file mode 100644 index 000000000..785050276 --- /dev/null +++ b/docs/private-dns/connect-devices/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 2, + "label": "How to connect devices", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/connect-devices/connect-devices.md b/docs/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/docs/private-dns/connect-devices/connect-devices.md @@ -0,0 +1,26 @@ +--- +title: General information +sidebar_position: 1 +toc_min_heading_level: 2 +toc_max_heading_level: 3 +--- + +In this section you will find instructions on how to connect your device to AdGuard DNS and learn about the main features of the service. + +- [Android](/private-dns/connect-devices/mobile-and-desktop/android.md) +- [iOS](/private-dns/connect-devices/mobile-and-desktop/ios.md) +- [macOS](/private-dns/connect-devices/mobile-and-desktop/macos.md) +- [Windows](/private-dns/connect-devices/mobile-and-desktop/windows.md) +- [Linux](/private-dns/connect-devices/mobile-and-desktop/linux.md) +- [Routers](/private-dns/connect-devices/routers/routers.md) +- [Game consoles](/private-dns/connect-devices/game-consoles/game-consoles.md) + +For devices that do not natively support encrypted DNS protocols, we offer three other options: + +- [AdGuard DNS Client](/dns-client/overview.md) +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) + +If you want to restrict access to AdGuard DNS to certain devices, use [DNS-over-HTTPS with authentication](/private-dns/connect-devices/other-options/doh-authentication.md). + +For connecting a large number of devices, there is an [automatic connection option](/private-dns/connect-devices/other-options/automatic-connection.md). diff --git a/docs/private-dns/connect-devices/game-consoles/_category_.json b/docs/private-dns/connect-devices/game-consoles/_category_.json new file mode 100644 index 000000000..7b910c736 --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 3, + "label": "Game consoles", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/connect-devices/game-consoles/game-consoles.md b/docs/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/game-consoles.md @@ -0,0 +1,12 @@ +--- +title: Game consoles +sidebar_position: 1 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +- [Nintendo](private-dns/connect-devices/game-consoles/nintendo.md) +- [Nintendo Switch](private-dns/connect-devices/game-consoles/nintendo-switch.md) +- [PlayStation](private-dns/connect-devices/game-consoles/playstation.md) +- [Steam Deck](/private-dns/connect-devices/game-consoles/steam.md) +- [Xbox One](private-dns/connect-devices/game-consoles/xbox-one.md) diff --git a/docs/private-dns/connect-devices/game-consoles/nintendo-switch.md b/docs/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..c79e7c0dc --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/nintendo-switch.md @@ -0,0 +1,29 @@ +--- +title: Nintendo Switch +sidebar_position: 3 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +It is likely that your router supports the use of encrypted DNS servers, so you can always configure Private AdGuard DNS on it and connect your game console to it. + +[How to configure your router](/private-dns/connect-devices/routers/routers.md) + +## Connect AdGuard DNS + +Configure your game console to use a public AdGuard DNS server or configure it via linked IP: + +1. Turn on your Nintendo Switch console and go to the home menu. +1. Go to *System Settings* → *Internet*. +1. Select the Wi-Fi network that you want to modify the DNS settings for. +1. Click *Change Settings* for the selected Wi-Fi network. +1. Scroll down and select *DNS Settings*. +1. In the *DNS Server* field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Save your DNS settings. + +It would be preferable to use linked IP (or dedicated IP if you have a Team subscription): + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/game-consoles/nintendo.md b/docs/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..29efa150f --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/nintendo.md @@ -0,0 +1,36 @@ +--- +title: Nintendo +sidebar_position: 2 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +It is likely that your router supports the use of encrypted DNS servers, so you can always configure Private AdGuard DNS on it and connect your game console to it. + +[How to configure your router](/private-dns/connect-devices/routers/routers.md) + +:::note Compatibility + +Applies to New Nintendo 3DS, New Nintendo 3DS XL, New Nintendo 2DS XL, Nintendo 3DS, Nintendo 3DS XL, and Nintendo 2DS. + +::: + +## Connect AdGuard DNS + +Configure your game console to use a public AdGuard DNS server or configure it via linked IP: + +1. From the home menu, select *System Settings*. +1. Go to *Internet Settings* → *Connection Settings*. +1. Select the connection file, then select *Change Settings*. +1. Select *DNS* → *Set Up*. +1. Set *Auto-Obtain DNS* to *No*. +1. Select *Detailed Setup* → *Primary DNS*. Hold down the left arrow to delete the existing DNS. +1. In the *DNS Server* field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Save the settings. + +It would be preferable to use linked IP (or dedicated IP if you have a Team subscription): + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/game-consoles/playstation.md b/docs/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..1183d612b --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/playstation.md @@ -0,0 +1,36 @@ +--- +title: PlayStation PS4/PS5 +sidebar_position: 4 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +It is likely that your router supports the use of encrypted DNS servers, so you can always configure Private AdGuard DNS on it and connect your game console to it. + +[How to configure your router](/private-dns/connect-devices/routers/routers.md) + +## Connect AdGuard DNS + +Configure your game console to use a public AdGuard DNS server or configure it via linked IP: + +1. Turn on your PS4/PS5 console and sign in to your account. +1. From the home screen, select the gear icon located in the top row. +1. In the *Settings* menu, select *Network*. +1. Select *Set Up Internet Connection*. +1. Choose *Use Wi-Fi* or *Use a LAN Cable*, depending on your network setup. +1. Select *Custom* and then select *Automatic* for *IP Address Settings*. +1. For *DHCP Host Name*, select *Do Not Specify*. +1. For *DNS Settings*, select *Manual*. +1. In the *DNS Server* field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Select *Next* to continue. +1. On the *MTU Settings* screen, select *Automatic*. +1. On the *Proxy Server* screen, select *Do Not Use*. +1. Select *Test Internet Connection* to test your new DNS settings. +1. Once the test is complete and you see "Internet Connection: Successful", save your settings. + +It would be preferable to use linked IP (or dedicated IP if you have a Team subscription): + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/game-consoles/steam.md b/docs/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..e6fdff634 --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/steam.md @@ -0,0 +1,29 @@ +--- +title: Steam Deck +sidebar_position: 5 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +It is likely that your router supports the use of encrypted DNS servers, so you can always configure Private AdGuard DNS on it and connect your game console to it. + +[How to configure your router](/private-dns/connect-devices/routers/routers.md) + +## Connect AdGuard DNS + +Configure your game console to use a public AdGuard DNS server or configure it via linked IP: + +1. Open the Steam Deck settings by clicking the gear icon in the upper right corner of the screen. +1. Click *Network*. +1. Click the gear icon next to the network connection you want to configure. +1. Select IPv4 or IPv6, depending on the type of network you're using. +1. Select *Automatic (DHCP) addresses only* or *Automatic (DHCP)*. +1. In the *DNS Server* field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Save the changes. + +It would be preferable to use linked IP (or dedicated IP if you have a Team subscription): + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/game-consoles/xbox-one.md b/docs/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..70f1703eb --- /dev/null +++ b/docs/private-dns/connect-devices/game-consoles/xbox-one.md @@ -0,0 +1,29 @@ +--- +title: Xbox One +sidebar_position: 6 +--- + +Game consoles do not support encrypted DNS, but they are well suited for setting up Public AdGuard DNS or Private AdGuard DNS via a linked IP address. + +It is likely that your router supports the use of encrypted DNS servers, so you can always configure Private AdGuard DNS on it and connect your game console to it. + +[How to configure your router](/private-dns/connect-devices/routers/routers.md) + +## Connect AdGuard DNS + +Configure your game console to use a public AdGuard DNS server or configure it via linked IP: + +1. Turn on your Xbox One console and sign in to your account. +1. Press the Xbox button on your controller to open the guide, then select *System* from the menu. +1. In the *Settings* menu, select *Network*. +1. Under *Network Settings*, select *Advanced Settings*. +1. Under *DNS Settings*, select *Manual*. +1. In the *DNS Server* field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Save the changes. + +It would be preferable to use linked IP (or dedicated IP if you have a Team subscription): + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/_category_.json b/docs/private-dns/connect-devices/mobile-and-desktop/_category_.json new file mode 100644 index 000000000..2b053eaed --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 1, + "label": "Mobile and desktop", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/android.md b/docs/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..031eda04b --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/android.md @@ -0,0 +1,79 @@ +--- +title: Android +sidebar_position: 2 +--- + +To connect an Android device to AdGuard DNS, first add it to *Dashboard*: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select Android. +1. Name the device. + ![Connecting device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/choose_android.png) + +## Use AdGuard Ad Blocker (paid option) + +The AdGuard app lets you use encrypted DNS, making it perfect for setting up AdGuard DNS on your Android device. You can choose from various encryption protocols. Along with DNS filtering, you also get an excellent ad blocker that works across your entire system. + +1. Install [the AdGuard app](https://adguard.com/adguard-android/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the app. +1. Tap the shield icon in the menu bar at the bottom of the screen. + ![Shield icon *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step3.png) +1. Tap *DNS protection*. + ![DNS protection *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +1. Select *DNS server*. + ![DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +1. Scroll down to *Custom servers* and tap *Add DNS server*. + ![Add DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step6.png) +1. Copy one of the following DNS addresses and paste it into the *Server adresses* field in the app. If you are not sure which one to use, select *DNS-over-HTTPS*. + ![DoH *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step7_1.png) + ![Custom DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step7_2.png) +1. Tap *Add*. +1. The DNS server you’ve added will appear at the bottom of the *Custom servers* list. To select it, tap its name or the radio button next to it. + ![Select DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step_9.png) +1. Tap *Save and select*. + ![Save and select *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step10.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use AdGuard VPN + +Not all VPN services support encrypted DNS. However, our VPN does, so if you need both a VPN and a private DNS, AdGuard VPN is your go-to option. + +1. Install [the AdGuard VPN app](https://adguard-vpn.com/android/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the app. +1. In the menu bar at the bottom of the screen, tap the gear icon. + ![Gear icon *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step3.png) +1. Open *App settings*. + ![App settings *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +1. Select *DNS server*. + ![DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +1. Scroll down and tap *Add a custom DNS server*. + ![Add a DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step6.png) +1. Copy one of the following DNS addresses and paste it into the *DNS servers adresses* field in the app. If you are not sure which one to use, select DNS-over-HTTPS. + ![DoH *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step7_1.png) + ![Custom DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step7_2.png) +1. Tap *Save and select*. + ![Add a DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step8.png) +1. The DNS server you’ve added will appear at the bottom of the *Custom DNS servers* list. + +All done! Your device is successfully connected to AdGuard DNS. + +## Configure Private DNS manually + +You can configure your DNS server in your device settings. Please note that Android devices only support DNS-over-TLS protocol. + +1. Go to *Settings* → *Wi-Fi & Internet* (or *Network and Internet*, depending on your OS version). + ![Settings *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_manual/manual_step1.png) +1. Select *Advanced* and tap *Private DNS*. + ![Private DNS *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_manual/manual_step2.png) +1. Select the *Private DNS provider hostname* option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +1. Tap *Save*. + ![Private DNS *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_manual/manual_step4.png) +All done! Your device is successfully connected to AdGuard DNS. + +## Configure plain DNS + +If you prefer not to use extra software for DNS configuration, you can opt for unencrypted DNS. You have two choices: using linked IPs or dedicated IPs. + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/ios.md b/docs/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..ba78757de --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/ios.md @@ -0,0 +1,82 @@ +--- +title: iOS +sidebar_position: 3 +--- + +To connect an iOS device to AdGuard DNS, first add it to *Dashboard*: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select iOS. +1. Name the device. + ![Connecting device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/choose_ios.png) + +## Use AdGuard Ad Blocker (paid option) + +The AdGuard app lets you use encrypted DNS, making it perfect for setting up AdGuard DNS on your iOS device. You can choose from various encryption protocols. Along with DNS filtering, you also get an excellent ad blocker that works across your entire system. + +1. Install the [AdGuard app](https://adguard.com/adguard-ios/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the AdGuard app. +1. Select the *Protection* tab in the bottom menu. + ![Shield icon *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step3.jpg) +1. Make sure that *DNS protection* is toggled on and then tap it. Choose *DNS server*. + ![DNS protection *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step4.jpg) + ![DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step4_2.jpg) +1. Scroll down to the bottom and tap *Add a custom DNS server*. + ![Add DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step5.jpg) +1. Copy one of the following DNS addresses and paste it into the *DNS server adress* field in the app. If you are not sure which one to prefer, choose DNS-over-HTTPS. + ![Copy server address *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step6_1.png) + ![Paste server address *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step6_2.jpg) +1. Tap *Save And Select*. + ![Save And Select *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step7.jpg) +1. Your freshly created server should appear at the bottom of the list. + ![Custom server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_ab/ios_step8.jpg) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use AdGuard VPN + +Not all VPN services support encrypted DNS. However, our VPN does, so if you need both a VPN and a private DNS, AdGuard VPN is your go-to option. + +1. Install the [AdGuard VPN app](https://adguard-vpn.com/ios/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the AdGuard VPN app. +1. Tap the gear icon in the bottom right corner of the screen. + ![Gear icon *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step3.jpg) +1. Open *General*. + ![General settings *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +1. Select *DNS server*. + ![DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +1. Scroll down to *Add custom DNS server*. + ![Add server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step6.png) +1. Copy one of the following DNS addresses and paste it into the *DNS server addresses* text field. If you are not sure which one to prefer, select *DNS-over-HTTPS*. + ![DoH server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step7_1.png) + ![Custom DNS server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step7_2.jpg) +1. Tap *Save*. + ![Save server *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +1. Your freshly created server should appear under *Custom DNS servers*. + ![Custom servers *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step9.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use a configuration profile + +An iOS device profile, also referred to as a "configuration profile" by Apple, is a certificate-signed XML file that you can manually install on your iOS device or deploy using an MDM solution. It also allows you to configure Private AdGuard DNS on your device. + +:::note Important + +If you are using a VPN, the configuration profile will be ignored. + +::: + +1. [Download](https://dns.website.agrd.dev/public_api/v1/settings/e7b499cc-94c0-4448-8404-88d11f4f51a2/doh_mobileconfig.xml) profile. +1. Open settings. +1. Tap *Profile Downloaded*. + ![Profile Downloaded *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +1. Tap *Install* and follow the onscreen instructions. + ![Install *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step4.png) + +## Configure plain DNS + +If you prefer not to use extra software to configure DNS, you can opt for unencrypted DNS. There are two options: using linked IPs or dedicated IPs. + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/linux.md b/docs/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..03014e8f9 --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/linux.md @@ -0,0 +1,110 @@ +--- +title: Linux +sidebar_position: 6 +--- + +To connect a Linux device to AdGuard DNS, first add it to *Dashboard*: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select Linux. +1. Name the device. + ![Connecting device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/choose_linux.png) + +## Use AdGuard DNS Client + +AdGuard DNS Client is a cross-platform console utility that allows you to use encrypted DNS protocols to access AdGuard DNS. + +You can learn more about this in the [related article](/dns-client/overview/). + +## Use AdGuard VPN CLI + +You can set up Private AdGuard DNS using the AdGuard VPN CLI (command-line interface). To get started with AdGuard VPN CLI, you’ll need to use Terminal. + +1. Install AdGuard VPN CLI by following [these instructions](https://adguard-vpn.com/kb/adguard-vpn-for-linux/installation/). +1. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +1. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +1. Activate the DNS settings by entering `adguardvpn-cli config set-system-dns on`. + +## Configure manually on Ubuntu (linked IP or dedicated IP required) + +1. Click *System* → *Preferences* → *Network Connections*. +1. Select the *Wireless* tab, then choose the network you’re connected to. +1. Click *Edit* → *IPv4*. +1. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +1. Turn off *Auto mode*. +1. Click *Apply*. +1. Go to *IPv6*. +1. Change the listed DNS addresses to the following addresses: + - `2a10:50c0:0:0:0:0:ded:ff` + - `2a10:50c0:0:0:0:0:dad:ff` +1. Turn off *Auto mode*. +1. Click *Apply*. +1. Link your IP address (or your dedicated IP if you have a Team subscription): + - [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) + - [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) + +## Configure manually on Debian (linked IP or dedicated IP required) + +1. Open the Terminal. +1. In the command line, type: `su`. +1. Enter your `admin` password. +1. In the command line, type: `nano /etc/resolv.conf`. +1. Change the listed DNS addresses to the following: + - IPv4: `94.140.14.49 and 94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff and 2a10:50c0:0:0:0:0:dad:ff` +1. Press *Ctrl + O* to save the document. +1. Press *Enter*. +1. Press *Ctrl + X* to save the document. +1. In the command line, type: `/etc/init.d/networking restart`. +1. Press *Enter*. +1. Close the Terminal. +1. Link your IP address (or your dedicated IP if you have a Team subscription): + - [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) + - [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) + +## Use dnsmasq + +1. Install dnsmasq using the following commands: + + `sudo apt updatesudo` + + `apt install` + + `dnsmasqsudo nano /etc/dnsmasq.conf` + +1. Use the following commands in dnsmasq.conf: + + `no-resolv` + + `bogus-priv` + + `strict-order` + + `server=94.140.14.49` + + `server=94.140.14.59` + + `port=5353` + + `add-cpe-id={Your_Device_ID}` + +1. Restart the dnsmasq service: + + `sudo service dnsmasq restart` + +All done! Your device is successfully connected to AdGuard DNS. + +:::note Important + +If you see a notification that you are not connected to AdGuard DNS, most likely the port on which dnsmasq is running is occupied by other services. Use [these instructions](https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#bindinuse) to solve the problem. + +::: + +## Use plain DNS + +If you prefer not to use extra software for DNS configuration, you can opt for unencrypted DNS. You have two choices: using linked IPs or dedicated IPs: + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/macos.md b/docs/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..dd47df08a --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/macos.md @@ -0,0 +1,81 @@ +--- +title: macOS +sidebar_position: 4 +--- + +To connect a macOS device to AdGuard DNS, first add it to *Dashboard*: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select Mac. +1. Name the device. + ![Connecting_device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/choose_mac.png) + +## Use AdGuard Ad Blocker (paid option) + +The AdGuard app lets you use encrypted DNS, making it perfect for setting up AdGuard DNS on your macOS device. You can choose from various encryption protocols. Along with DNS filtering, you also get an excellent ad blocker that works across your entire system. + +1. [Install the app](https://adguard.com/adguard-mac/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the app. +1. Click the icon in the top right corner. + ![Protection icon *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step3.png) +1. Select *Preferences...*. + ![Preferences *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +1. Click the *DNS* tab from the top row of icons. + ![DNS tab *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step5.png) +1. Enable DNS protection by ticking the box at the top. + ![DNS protection *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step6.png) +1. Click *+* in the bottom left corner. + ![Click + *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +1. Copy one of the following DNS addresses and paste it into the *DNS servers* field in the app. If you are not sure which one to prefer, select *DNS-over-HTTPS*. + ![DoH server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step8_1.png) + ![Create server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step8_2.png) +1. Click *Save and Choose*. + ![Save and Choose *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +1. Your newly created server should appear at the bottom of the list. + ![Providers *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step10.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use AdGuard VPN + +Not all VPN services support encrypted DNS. However, our VPN does, so if you need both a VPN and a private DNS, AdGuard VPN is your go-to option. + +1. Install the [AdGuard VPN app](https://adguard-vpn.com/mac/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the AdGuard VPN app. +1. Open *Settings* → *App settings* → *DNS servers* → *Add Custom Server*. + ![Add custom server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_vpn/mac_step3.png) +1. Copy one of the following DNS addresses and paste it into the *DNS server addresses* text field. If you are not sure which one to prefer, select DNS-over-HTTPS. + ![DNS servers *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_vpn/mac_step4.png) +1. Click *Save and select*. +1. The DNS server you’ve added will appear at the bottom of the *Custom DNS servers* list. + ![Custom DNS servers *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_vpn/mac_step6.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use a configuration profile + +A macOS device profile, also referred to as a "configuration profile" by Apple, is a certificate-signed XML file that you can manually install on your device or deploy using an MDM solution. It also allows you to configure Private AdGuard DNS on your device. + +:::note Important + +If you are using a VPN, the configuration profile will be ignored. + +::: + +1. On the device that you want to connect to AdGuard DNS, download the configuration profile. +1. Choose Apple menu → *System Settings*, click *Privacy & Security* in the sidebar, then click *Profiles* on the right (you may need to scroll down). + ![Profile Downloaded *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_profile/mac_step2.png) +1. In the *Downloaded* section, double-click the profile. + ![Downloaded *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_profile/mac_step3.png) +1. Review the profile contents and click *Install*. + ![Install *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_profile/mac_step4.png) +1. Enter the admin password and click *OK*. + +All done! Your device is successfully connected to AdGuard DNS. + +## Configure plain DNS + +If you prefer not to use extra software for DNS configuration, you can opt for unencrypted DNS. You have two choices: using linked IPs or dedicated IPs. + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/mobile-and-desktop/windows.md b/docs/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..43a37a88a --- /dev/null +++ b/docs/private-dns/connect-devices/mobile-and-desktop/windows.md @@ -0,0 +1,68 @@ +--- +title: Windows +sidebar_position: 5 +--- + +To connect an iOS device to AdGuard DNS, first add it to *Dashboard*: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select Windows. +1. Name the device. + ![Connecting_device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/choose_windows.png) + +## Use AdGuard Ad Blocker (paid option) + +The AdGuard app lets you use encrypted DNS, making it perfect for setting up AdGuard DNS on your Windows device. You can choose from various encryption protocols. Along with DNS filtering, you also get an excellent ad blocker that works across your entire system. + +1. [Install the app](https://adguard.com/adguard-windows/overview.html) on the device you want to connect to AdGuard DNS. +1. Open the app. +1. Click *Settings* at the top of the app's home screen. + ![Settings *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step3.png) +1. Select the *DNS Protection* tab from the menu on the left. + ![DNS protection *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step4.png) +1. Click your currently selected DNS server. + ![DNS server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step5.png) +1. Scroll down and click *Add a custom DNS server*. + ![Add a custom DNS server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step6.png) +1. In the DNS upstreams field, paste one of the following addresses. If you’re not sure which one to prefer, choose DNS-over-HTTPS. + ![DoH server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step7_1.png) + ![Create server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step7_2.png) +1. Click *Save and select*. + ![Save and select *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +1. The DNS server you’ve added will appear at the bottom of the *Custom DNS servers* list. + ![Custom DNS servers *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step9.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use AdGuard VPN + +Not all VPN services support encrypted DNS. However, our VPN does, so if you need both a VPN and a private DNS, AdGuard VPN is your go-to option. + +1. Install AdGuard VPN. +1. Open the app and click *Settings*. +1. Select *App settings*. + ![App settings *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +1. Scroll down and select *DNS servers*. + ![DNS servers *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step5.png) +1. Click *Add custom DNS server*. + ![Add custom DNS server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step6.png) +1. In the *Server address* field, paste one of the following addresses. If you’re not sure which one to prefer, select DNS-over-HTTPS. + ![DoH server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step7_1.png) + ![Create server *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step7_2.png) +1. Click *Save and select*. + ![Save and select *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step8.png) + +All done! Your device is successfully connected to AdGuard DNS. + +## Use AdGuard DNS Client + +AdGuard DNS Client is a versatile, cross-platform console tool that allows you to connect to AdGuard DNS using encrypted DNS protocols. + +More details can be found in [different article](/dns-client/overview/). + +## Configure plain DNS + +If you prefer not to use extra software for DNS configuration, you can opt for unencrypted DNS. You have two choices: using linked IPs or dedicated IPs. + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/other-options/_category_.json b/docs/private-dns/connect-devices/other-options/_category_.json new file mode 100644 index 000000000..199a70b40 --- /dev/null +++ b/docs/private-dns/connect-devices/other-options/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 4, + "label": "Other options", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/connect-devices/other-options/automatic-connection.md b/docs/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..1c6c6ca24 --- /dev/null +++ b/docs/private-dns/connect-devices/other-options/automatic-connection.md @@ -0,0 +1,59 @@ +--- +title: Automatic connection +sidebar_position: 5 +--- + +## Why it is useful + +Not everyone feels at ease adding devices through the Dashboard. For instance, if you’re a system administrator setting up multiple corporate devices simultaneously, you’ll want to minimize manual tasks as much as possible. + +You can create a connection link and use it in the device settings. Your device will be detected and automatically connected to the server. + +## How to configure automatic connection + +1. Open the *Dashboard* and select the required server. +1. Go to *Devices*. +1. Enable the option to connect devices automatically. + ![Connect devices automatically *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step4.png) + +Now you can automatically connect your device to the server by creating a special address that includes the device name, device type, and current server ID. Let’s explore what these addresses look like and the rules for creating them. + +### Examples of automatic connection addresses + +- `tls://adr-{Your_Server_ID}-AdGuard-Test-Device.d.adguard-dns.com` — this will automatically create an `Android` device with the `DNS-over-TLS` protocol named `AdGuard Test Device` + +- `https://d.adguard-dns.com/dns-query/win-{Your_Server_ID}-John-Doe` — this will automatically create a `Windows` device with the `DNS-over-HTTPS` protocol named `John Doe` + +- `quic://ios-73f78a1d-Mary-Sue.d.adguard-dns.com` — this will automatically create a `iOS` device with the `DNS-over-QUIC` protocol named `Mary Sue` + +### Naming conventions + +When creating devices manually, please note that there are restrictions related to name length, characters, spaces, and hyphens. + +**Name length**: 50 characters maximum. Characters beyond this limit are ignored. + +**Permitted characters**: English letters, numbers, and hyphens `-`. Other characters are ignored. + +**Spaces and hyphens**: Use a hyphen for a space and a double hyphen ( `--`) for a hyphen. + +**Device type**: Use the following abbreviations: + +- Windows — `win` +- macOS — `mac` +- Android — `adr` +- iOS — `ios` +- Linux — `lnx` +- Router — `rtr` +- Smart TV — `stv` +- Game console — `gam` +- Other — `otr` + +## Link generator + +We’ve added a template that generates a link for the specific device type and protocol. + +1. Go to *Servers* → *Server settings* → *Devices* → *Connect devices automatically* and click *Link generator and instructions*. +1. Select the protocol you want to use as well as the device name and the device type. +1. Click *Generate link*. + ![Generate link *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +1. You have successfully generated the link, now copy the server address and use it in one of the [AdGuard apps](https://adguard.com/welcome.html) diff --git a/docs/private-dns/connect-devices/other-options/dedicated-ip.md b/docs/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..bae93c84b --- /dev/null +++ b/docs/private-dns/connect-devices/other-options/dedicated-ip.md @@ -0,0 +1,32 @@ +--- +title: Dedicated IPs +sidebar_position: 2 +--- + +## What are dedicated IPs? + +Dedicated IPv4 addresses are available to users with Team and Enterprise subscriptions, while linked IPs are available to everyone. + +If you have a Team or Enterprise subscription, you'll receive several personal dedicated IP addresses. Requests to these addresses are treated as "yours," and server-level configurations and filtering rules are applied accordingly. Dedicated IP addresses are much more secure and easier to manage. With linked IPs, you have to manually reconnect or use a special program every time the device's IP address changes, which happens after every reboot. + +## Why do you need a dedicated IP? + +Unfortunately, the technical specifications of the connected device may not always allow you to set up an encrypted private AdGuard DNS server. In this case, you will have to use standard unencrypted DNS. There are two ways to set up AdGuard DNS: [using linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) and using dedicated IPs. + +Dedicated IPs are generally a more stable option. Linked IP has some limitations, such as only residential addresses are allowed, your provider can change the IP, and you'll need to relink the IP address. With dedicated IPs, you get an IP address that is exclusively yours, and all requests will be counted for your device. + +The disadvantage is that you may start receiving irrelevant traffic (scanners, bots), as always happens with public DNS resolvers. You may need to use [Access settings](/private-dns/server-and-settings/access.md) to limit bot traffic. + +The instructions below explain how to connect a dedicated IP to the device: + +## Connect AdGuard DNS using dedicated IPs + +1. Open Dashboard. +1. Add a new device or open the settings of a previously created device. +1. Select *Use server addresses*. +1. Next, open *Plain DNS Server Addresses*. +1. Select the server you wish to use. +1. To bind a dedicated IPv4 address, click *Assign*. +1. If you want to use a dedicated IPv6 address, click *Copy*. + ![Copy address *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/dedicated_step7.png) +1. Copy and paste the selected dedicated address into the device configurations. diff --git a/docs/private-dns/connect-devices/other-options/doh-authentication.md b/docs/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..6378c3059 --- /dev/null +++ b/docs/private-dns/connect-devices/other-options/doh-authentication.md @@ -0,0 +1,28 @@ +--- +title: DNS-over-HTTPS with authentication +sidebar_position: 4 +--- + +## Why it is useful + +DNS-over-HTTPS with authentication allows you to set a username and password for accessing your chosen server. + +This helps prevent unauthorized users from accessing it and enhances security. Additionally, you can restrict the use of other protocols for specific profiles. This feature is particularly useful when your DNS server address is known to others. By adding a password, you can block access and ensure that only you can use it. + +## How to set it up + +:::note Compatibility + +This feature is supported by [AdGuard DNS Client](/dns-client/overview.md) as well as [AdGuard apps](https://adguard.com/welcome.html). + +::: + +1. Open Dashboard. +1. Add a device or go to the settings of a previously created device. +1. Click *Use DNS server addresses* and open the *Encrypted DNS server addresses* section. +1. Configure DNS-over-HTTPS with authentication as you like. +1. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +1. To do this, copy the address of the encrypted server and paste it into the AdGuard app or AdGuard DNS Client settings. + ![Copy address *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/doh_step6.png) +1. You can also deny the use of other protocols. + ![Deny protocols *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/deny_protocol.png) diff --git a/docs/private-dns/connect-devices/other-options/linked-ip.md b/docs/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..879a905b7 --- /dev/null +++ b/docs/private-dns/connect-devices/other-options/linked-ip.md @@ -0,0 +1,96 @@ +--- +title: Linked IPs +sidebar_position: 3 +--- + +## What linked IPs are and why they are useful + +Not all devices can support encrypted DNS protocols. In this case, users should consider setting up unencrypted DNS. + +You can use a **linked IP address**: in this setup, the service will consider all standard DNS queries coming from that IP address and for that specific device. The only requirement for a linked IP address is that it must be a residential IP. + +:::note + +A **residential IP address** is assigned to a device connected to a residential ISP. It's usually tied to a physical location and given to individual homes or apartments. People use residential IP addresses for everyday online activities like browsing the web, sending emails, using social media, or streaming content. + +::: + +Sometimes, a residential IP address may already be in use, and if you try to connect to it, AdGuard DNS will prevent the connection. +![Linked IPv4 address *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/linked.png) +If that happens, please reach out to support at [support@adguard-dns.io](mailto:support@adguard-dns.io), and they’ll assist you with the right configuration settings. + +## How to set up linked IP + +The following instructions explain how to connect to the device via **linking IP address**: + +1. Open Dashboard. +1. Add a new device or open the settings of a previously connected device. +1. Go to *Use DNS server addresses*. +1. Open *Plain DNS server addresses* and connect the linked IP. + ![Linked IP *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/linked_step4.png) + +## Dynamic DNS: Why it is useful + +Every time a device connects to the network, it gets a new dynamic IP address. When a device disconnects, the DHCP server reassigns IP addresses to the remaining devices. This means dynamic IP addresses can change frequently and unpredictably. Consequently, you'll need to update settings whenever the device is rebooted or the network changes. + +To automatically keep the linked IP address updated, you can use DNS. AdGuard DNS will regularly check the IP address of your DDNS domain and link it to your server. + +:::note + +Dynamic DNS (DDNS) is a service that automatically updates DNS records whenever your IP address changes. It converts network IP addresses into easy-to-read domain names for convenience. The information that connects a name to an IP address is stored in a table on the DNS server. DDNS updates these records whenever there are changes to the IP addresses. + +::: + +This way, you won’t have to manually update the associated IP address each time it changes. + +## Dynamic DNS: How to set it up + +1. First, you need to check if DDNS is supported by your router settings: + - Go to *Router settings* → *Network* + - Locate the DDNS or the *Dynamic DNS* section + - Navigate to it and verify that the settings are indeed supported. *This is just an example of what it may look like. It may vary depending on your router* + ![DDNS supported *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/dynamic_dns.png) +1. Register your domain with a popular service like [DynDNS](https://dyn.com/remote-access/), [NO-IP](https://www.noip.com/), or any other DDNS provider you prefer. +1. Enter the domain in your router settings and sync the configurations. +1. Go to the Linked IP settings to connect the address, then navigate to *Advanced Settings* and click *Configure DDNS*. +1. Input the domain you registered earlier and click *Configure DDNS*. + ![Configure DDNS *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/dns_supported.png) + +All done, you've successfully set up DDNS! + +## Automation of linked IP update via script + +### On Windows + +The easiest way is to use the Task Scheduler: + +1. Create a task: + - Open the Task Scheduler. + - Create a new task. + - Set the trigger to run every 5 minutes. + - Select *Run Program* as the action. +1. Select a program: + - In the *Program or Script* field, type `powershell' + - In the *Add Arguments* field, type: + - `Command "Invoke-WebRequest -Uri 'https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}'"` +1. Save the task. + +### On macOS and Linux + +On macOS and Linux, the easiest way is to use `cron`: + +1. Open crontab: + - In the terminal, run `crontab -e`. +1. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +1. Save crontab. + +:::note Important + +- Make sure you have `curl` installed on macOS and Linux. +- Remember to copy the address from the settings and replace the `ServerID` and `UniqueKey`. +- If more complex logic or processing of query results is required, consider using scripts (e.g. Bash, Python) in conjunction with a task scheduler or cron. + +::: diff --git a/docs/private-dns/connect-devices/routers/_category_.json b/docs/private-dns/connect-devices/routers/_category_.json new file mode 100644 index 000000000..686e1f35c --- /dev/null +++ b/docs/private-dns/connect-devices/routers/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 2, + "label": "Routers", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/connect-devices/routers/asus.md b/docs/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..1999485a7 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/asus.md @@ -0,0 +1,42 @@ +--- +title: Asus +sidebar_position: 3 +--- + +## Configure DNS-over-TLS + +These are general instructions for configuring Private AdGuard DNS for Asus routers. + +The configuration information in these instructions is taken from a specific router model, so it may differ from the interface of an individual device. + +If necessary: Configure DNS-over-TLS on ASUS, install the [ASUS Merlin firmware](https://www.asuswrt-merlin.net/download) suitable for your router version on your computer. + +1. Log in to your Asus router admin panel. It can be accessed via [http://router.asus.com](http://router.asus.com/), [http://192.168.1.1](http://192.168.1.1/), [http://192.168.0.1](http://192.168.0.1/), or [http://192.168.2.1](http://192.168.2.1/). +1. Enter the administrator username (usually, it’s admin) and router password. +1. In the *Advanced Settings* sidebar, navigate to the WAN section. +1. In the *WAN DNS Settings* section, set *Connect to DNS Server automatically* to *No*. +1. Set *Forward local queries*, *Enable DNS Rebind*, and *Enable DNSSEC* to *No*. +1. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +1. Make sure the *DNS-over-TLS Profile* is set to *Strict*. +1. Scroll down to the *DNS-over-TLS Servers List* section. In the *Address* field, enter one of the addresses below: + - `94.140.14.49` and `94.140.14.59` +1. For *TLS Port*, enter 853. +1. In the *TLS Hostname* field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +1. Scroll to the bottom of the page and click *Apply*. + +## Use your router admin panel + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Advanced Settings* or *Advanced*. +1. Select *WAN* or *Internet*. +1. Open *DNS Settings* or *DNS*. +1. Choose *Manual DNS*. Select *Use These DNS Servers* or *Specify DNS Server Manually* and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/fritzbox.md b/docs/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..b0a69d947 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/fritzbox.md @@ -0,0 +1,33 @@ +--- +title: FritzBox +sidebar_position: 4 +--- + +FRITZ!Box provides maximum flexibility for all devices by simultaneously using the 2.4 GHz and 5 GHz frequency bands. All devices connected to the FRITZ!Box are fully protected against attacks from the Internet. The configuration of this brand of routers also allows you to set up encrypted Private AdGuard DNS. + +## Configure DNS-over-TLS + +1. Open the router admin panel. It can be accessed at fritz.box, the IP address of your router, or `192.168.178.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Internet* or *Home Network*. +1. Select *DNS* or *DNS Settings*. +1. Under DNS-over-TLS (DoT), check *Use DNS-over-TLS* if supported by the provider. +1. Select *Use Custom TLS Server Name Indication (SNI)* and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +1. Save the settings. + +## Use your router admin panel + +Use this guide if your FritzBox router does not support DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Internet* or *Home Network*. +1. Select *DNS* or *DNS Settings*. +1. Select *Manual DNS*, then *Use These DNS Servers* or *Specify DNS Server Manually*, and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/keenetic.md b/docs/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..695160cbf --- /dev/null +++ b/docs/private-dns/connect-devices/routers/keenetic.md @@ -0,0 +1,48 @@ +--- +title: Keenetic +sidebar_position: 5 +--- + +Keenetic routers are known for their stability and flexible configurations, and are easy to set up, allowing you to easily install encrypted Private AdGuard DNS on your device. + +## Configure DNS-over-HTTPS + +1. Open the router admin panel. It can be accessed at my.keenetic.net, the IP address of your router, or `192.168.1.1`. +1. Press the menu button at the bottom of the screen and select *Management*. +1. Open *System settings*. +1. Press *Component options* → *System component options*. +1. In *Utilities and services*, select DNS-over-HTTPS proxy and install it. +1. Head to *Menu* → *Network rules* → *Internet safety*. +1. Navigate to DNS-over-HTTPS servers and click *Add DNS-over-HTTPS server*. +1. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +1. Click *Save*. + +## Configure DNS-over-TLS + +1. Open the router admin panel. It can be accessed at my.keenetic.net, the IP address of your router, or `192.168.1.1`. +1. Press the menu button at the bottom of the screen and select *Management*. +1. Open *System settings*. +1. Press *Component options* → *System component options*. +1. In *Utilities and services*, select DNS-over-HTTPS proxy and install it. +1. Head to *Menu* → *Network rules* → *Internet safety*. +1. Navigate to DNS-over-HTTPS servers and click *Add DNS-over-HTTPS server*. +1. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +1. Click *Save*. + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Internet* or *Home Network*. +1. Select *WAN* or *Internet*. +1. Select *DNS* or *DNS Settings*. +1. Choose *Manual DNS*. Select *Use These DNS Servers* or *Specify DNS Server Manually* and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/mikrotik.md b/docs/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..31faffcc1 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/mikrotik.md @@ -0,0 +1,60 @@ +--- +title: MikroTik +sidebar_position: 6 +--- + +MikroTik routers use the open source RouterOS operating system, which provides routing, wireless networking and firewall services for home and small office networks. + +## Configure DNS-over-HTTPS + +1. Access your MikroTik router: + - Open your web browser and go to your router's IP address (usually `192.168.88.1`) + - Alternatively, you can use Winbox to connect to your MikroTik router + - Enter your administrator username and password +1. Import root certificate: + - Download the latest bundle of trusted root certificates: [https://curl.se/docs/caextract.html](https://curl.se/docs/caextract.html) + - Navigate to *Files*. Click *Upload* and select the downloaded cacert.pem certificate bundle + - Go to *System* → *Certificates* → *Import* + - In the *File Name* field, choose the uploaded certificate file + - Click *Import* +1. Configure DNS-over-HTTPS: + - Go to *IP* → *DNS* + - In the *Servers* section, add the following AdGuard DNS servers: + - `94.140.14.49` + - `94.140.14.59` + - Set *Allow Remote Requests* to *Yes* (this is crucial for DoH to function) + - In the *Use DoH server* field, enter the URL of the private AdGuard DNS server: `https://d.adguard-dns.com/dns-query/*******` + - Click *OK* +1. Create Static DNS Records: + - In the *DNS Settings*, click *Static* + - Click *Add New* + - Set *Name* to d.adguard-dns.com + - Set *Type* to A + - Set *Address* to `94.140.14.49` + - Set *TTL* to 1d 00:00:00 + - Repeat the process to create an identical entry, but with *Address* set to `94.140.14.59` +1. Disable Peer DNS on DHCP Client: + - Go to *IP* → *DHCP Client* + - Double-click the client used for your Internet connection (usually on the WAN interface) + - Uncheck *Use Peer DNS* + - Click *OK* +1. Link your IP. +1. Test and verify: + - You might need to reboot your MikroTik router for all changes to take effect + - Clear your browser's DNS cache. You can use a tool like [https://www.dnsleaktest.com](https://www.dnsleaktest.com/) to check if your DNS requests are now routed through AdGuard + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Webfig* → *IP* → *DNS*. +1. Select *Servers* and enter one of the following DNS server addresses. + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/openwrt.md b/docs/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..6e5067c1b --- /dev/null +++ b/docs/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,89 @@ +--- +title: OpenWRT +sidebar_position: 7 +--- + +OpenWRT routers use an open source, Linux-based operating system that provides the flexibility to configure routers and gateways according to user preferences. The developers took care to add support for encrypted DNS servers, allowing you to configure Private AdGuard DNS on your device. + +## Configure DNS-over-HTTPS + +- **Command-line instructions**. Install the required packages. DNS encryption should be enabled automatically. + + ```# Install packages + 1. opkg update2. + 2. opkg install https-dns-proxy + +- **Web interface**. If you want to manage the settings using web interface, install the necessary packages. + + ```# Install packages + 1. opkg update + 2. opkg install luci-app-https-dns-proxy + 3. /etc/init.d/rpcd restart + +Navigate to *LuCI* → *Services* → *HTTPS DNS Proxy* to configure the https-dns-proxy. + +- **Configure DoH provider**. https-dns-proxy is configured with Google DNS and Cloudflare DNS by default. You need to change it to AdGuard DoH. Specify several resolvers to improve fault tolerance. + + ```# Configure DoH provider + 1. while uci -q delete https-dns-proxy.@https-dns-proxy[0]; do :; done + 2. uci set https-dns-proxy.dns="https-dns-proxy" + 3. uci set https-dns-proxy.dns.bootstrap_dns="94.140.14.49,94.140.14.59" + 4. uci set https-dns-proxy.dns.resolver_url="https://d.adguard-dns.com/dns-query/{Your_Private_Server_ID}" + 5. uci set https-dns-proxy.dns.listen_addr="127.0.0.1" + 6. uci set https-dns-proxy.dns.listen_port="5053" + 7. uci commit https-dns-proxy + 8. /etc/init.d/https-dns-proxy restart + +## Configure DNS-over-TLS + +- **Command-line instructions**. [Disable](https://openwrt.org/docs/guide-user/base-system/dhcp_configuration#disabling_dns_role) Dnsmasq DNS role or remove it completely optionally [replacing](https://openwrt.org/docs/guide-user/base-system/dhcp_configuration#replacing_dnsmasq_with_odhcpd_and_unbound) its DHCP role with odhcpd. + + ```# Install packages + 1. opkg update + 2. opkg install unbound-daemon ca-certificates + +LAN clients and the local system should use Unbound as a primary resolver assuming that Dnsmasq is disabled. + +- **Web interface**. If you want to manage the settings using web interface, install the necessary packages. + + ```# Install packages + 1. opkg update + 2. opkg install luci-app-unbound ca-certificates + 3. /etc/init.d/rpcd restart + +Navigate to *LuCI* → *Services* → *Recursive DNS* to configure Unbound. + +- **Configure AdGuard DNS-over-TLS**. + + ```1. uci add unbound zone + 2. uci set unbound.@zone[-1].enabled="1" + 3. uci set unbound.@zone[-1].fallback="0" + 4. uci set unbound.@zone[-1].zone_type="forward_zone" + 5. uci add_list unbound.@zone[-1].zone_name="." + 6. uci set unbound.@zone[-1].tls_upstream="1" + 7. uci set unbound.@zone[-1].tls_index="{Your_Private_Server_ID}.d.adguard-dns.com" + 8. uci add_list unbound.@zone[-1].server="94.140.14.49" + 9. uci add_list unbound.@zone[-1].server="94.140.14.59" + 10. uci add_list unbound.@zone[-1].server="2a10:50c0::ded:ff" + 11. uci add_list unbound.@zone[-1].server="2a10:50c0::dad:ff" + 12. uci commit unbound + 13. /etc/init.d/unbound restart + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Network* → *Interfaces*. +1. Select your Wi-Fi network or wired connection. +1. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +1. Under *Use custom DNS servers*, enter the IP addresses of the DNS servers you want to use. You can enter multiple DNS servers, separated by spaces or commas: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/opnsense.md b/docs/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..d038590fc --- /dev/null +++ b/docs/private-dns/connect-devices/routers/opnsense.md @@ -0,0 +1,25 @@ +--- +title: OPNSense +sidebar_position: 8 +--- + +OPNSense firmware is often used to configure wireless access points, DHCP servers, DNS servers, allowing you to configure AdGuard DNS directly on the device. + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Click *Services* in the top menu, then select *DHCP Server* from the drop-down menu. +1. On the *DHCP Server* page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +1. Scroll down to *DNS Servers*. +1. Choose *Manual DNS*. Select *Use These DNS Servers* or *Specify DNS Server Manually* and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Optionally, you can enable DNSSEC for enhanced security. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/routers.md b/docs/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..0ed42fdf0 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Routers +sidebar_position: 1 +toc_min_heading_level: 2 +toc_max_heading_level: 3 +--- + +First you need to add your router to the AdGuard DNS interface: + +1. Go to *Dashboard* and click *Connect new device*. +1. In the drop-down menu *Device type*, select Router. +1. Select router brand and name the device. + ![Connecting device *mobile_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/choose_router.png) + +Below are instructions for different router models. Please select the one you need: + +- [Universal instructions](/private-dns/connect-devices/routers/universal.md) +- [Asus](/private-dns/connect-devices/routers/asus.md) +- [FritzBox](/private-dns/connect-devices/routers/fritzbox.md) +- [Keenetic](/private-dns/connect-devices/routers/keenetic.md) +- [MikroTik](/private-dns/connect-devices/routers/mikrotik.md) +- [OpenWRT](/private-dns/connect-devices/routers/openwrt.md) +- [OpenSense](/private-dns/connect-devices/routers/opnsense.md) +- [Synology NAS](/private-dns/connect-devices/routers/synology-nas.md) +- [Unifi](/private-dns/connect-devices/routers/unifi.md) +- [Xiaomi](/private-dns/connect-devices/routers/xiaomi.md) diff --git a/docs/private-dns/connect-devices/routers/synology-nas.md b/docs/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..d0f6f9ed3 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/synology-nas.md @@ -0,0 +1,24 @@ +--- +title: Synology NAS +sidebar_position: 9 +--- + +Synology NAS routers are incredibly easy to use and can be combined into a single mesh network. You can manage your network remotely anytime, anywhere. You can also configure AdGuard DNS directly on the router. + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.1.1` or `192.168.0.1`. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Control Panel* or *Network*. +1. Select *Network Interface* or *Network Settings*. +1. Select your Wi-Fi network or wired connection. +1. Choose *Manual DNS*. Select *Use These DNS Servers* or *Specify DNS Server Manually* and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/unifi.md b/docs/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..578aabd0d --- /dev/null +++ b/docs/private-dns/connect-devices/routers/unifi.md @@ -0,0 +1,29 @@ +--- +title: UniFi +sidebar_position: 10 +--- + +The UiFi router (commonly known as Ubiquiti's UniFi series) has a number of advantages that make it particularly suitable for home, business, and enterprise environments. Unfortunately, it does not support encrypted DNS, but it is great for setting up AdGuard DNS via linked IP. + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Log in to the Ubiquiti UniFi controller. +1. Go to *Settings* → *Networks*. +1. Click *Edit Network* → *WAN*. +1. Proceed to *Common Settings* → *DNS Server* and enter the following DNS server addresses. + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Click *Save*. +1. Return to *Network*. +1. Choose *Edit Network* → *LAN*. +1. Find *DHCP Name Server* and select *Manual*. +1. Enter your gateway address in the *DNS Server 1* field. Alternatively, you can enter the AdGuard DNS server addresses in *DNS Server 1* and *DNS Server 2* fields: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/universal.md b/docs/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..f77500b70 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,29 @@ +--- +title: Universal instructions +sidebar_position: 2 +--- + +Here are some general instructions for setting up Private AdGuard DNS on routers. You can refer to this guide if you can't find your specific router in the main list. Please note that the configuration details provided here are approximate and may differ from the settings on your particular model. + +## Use your router admin panel + +1. Open the preferences for your router. Usually you can access them from your browser. Depending on the model of your router, try entering one the following addresses: + - Linksys and Asus routers typically use: [http://192.168.1.1](http://192.168.1.1/) + - Netgear routers typically use: [http://192.168.0.1](http://192.168.0.1/) or [http://192.168.1.1](http://192.168.1.1/) D-Link routers typically use [http://192.168.0.1](http://192.168.0.1/) + - Ubiquiti routers typically use: [http://unifi.ubnt.com](http://unifi.ubnt.com/) +1. Enter the router's password. + + :::note Important + + If the password is unknown, you can often reset it by pressing a button on the router; it will also reset the router to its factory settings. Some models have a dedicated management application, which should already be installed on your computer. + + ::: + +1. Find where DNS settings are located in the router's admin console. Change the listed DNS addresses to the following addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/connect-devices/routers/xiaomi.md b/docs/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..03d51ea23 --- /dev/null +++ b/docs/private-dns/connect-devices/routers/xiaomi.md @@ -0,0 +1,25 @@ +--- +title: Xiaomi +sidebar_position: 11 +--- + +Xiaomi routers have a lot of advantages: Steady strong signal, network security, stable operation, intelligent management, at the same time, the user can connect up to 64 devices to the local Wi-Fi network. + +Unfortunately, it doesn't support encrypted DNS, but it's great for setting up AdGuard DNS via linked IP. + +## Use your router admin panel + +Use these instructions if your Keenetic router does not support DNS-over-HTTPS or DNS-over-TLS configuration: + +1. Open the router admin panel. It can be accessed at `192.168.31.1` or the IP address of your router. +1. Enter the administrator username (usually, it’s admin) and router password. +1. Open *Advanced Settings* or *Advanced*, depending on your router model. +1. Open *Network* or *Internet* and look for DNS or DNS Settings. +1. Choose *Manual DNS*. Select *Use These DNS Servers* or *Specify DNS Server Manually* and enter the following DNS server addresses: + - IPv4: `94.140.14.49` and `94.140.14.59` + - IPv6: `2a10:50c0:0:0:0:0:ded:ff` and `2a10:50c0:0:0:0:0:dad:ff` +1. Save the settings. +1. Link your IP (or your dedicated IP if you have a Team subscription). + +- [Dedicated IPs](/private-dns/connect-devices/other-options/dedicated-ip.md) +- [Linked IPs](/private-dns/connect-devices/other-options/linked-ip.md) diff --git a/docs/private-dns/overview.md b/docs/private-dns/overview.md index 7626564fc..275c714ac 100644 --- a/docs/private-dns/overview.md +++ b/docs/private-dns/overview.md @@ -38,7 +38,7 @@ Here is a simple comparison of features available in public and private AdGuard | - | Detailed query log | | - | Parental control | -## How to set up private AdGuard DNS + + +### How to connect devices to AdGuard DNS + +AdGuard DNS is very flexible and can be set up on various devices including tablets, PCs, routers, and game consoles. This section provides detailed instructions on how to connect your device to AdGuard DNS. + +[How to connect devices to AdGuard DNS](/private-dns/connect-devices/connect-devices.md) + +### Server and settings + +This section explains what a "server" is in AdGuard DNS and what settings are available. The settings allow you to customise how AdGuard DNS responds to blocked domains and manage access to your DNS server. + +[Server and settings](/private-dns/server-and-settings/server-and-settings.md) + +### How to set up filtering + +In this section we describe a number of settings that allow you to fine-tune the functionality of AdGuard DNS. Using blocklists, user rules, parental controls and security filters, you can configure filtering to suit your needs. + +[How to set up filtering](/private-dns/setting-up-filtering/blocklists.md) + +### Statistics and Query log + +Statistics and Query log provide insight into the activity of your devices. The *Statistics* tab allows you to view a summary of DNS requests made by devices connected to your Private AdGuard DNS. In the Query log, you can view information about each request and also sort requests by status, type, company, device, time, and country. + +[Statistics and Query log](/private-dns/statistics-and-log/statistics.md) diff --git a/docs/private-dns/server-and-settings/_category_.json b/docs/private-dns/server-and-settings/_category_.json new file mode 100644 index 000000000..a9d5546d6 --- /dev/null +++ b/docs/private-dns/server-and-settings/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 3, + "label": "Server and settings", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/server-and-settings/access.md b/docs/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..028a2db1d --- /dev/null +++ b/docs/private-dns/server-and-settings/access.md @@ -0,0 +1,32 @@ +--- +title: Access settings +sidebar_position: 3 +--- + +By configuring Access settings, you can protect your AdGuard DNS from unauthorized access. For example, you are using a dedicated IPv4 address, and attackers using sniffers have recognized it and are bombarding it with requests. No problem, just add the pesky domain or IP address to the list and it won't bother you anymore! + +Blocked requests will not be displayed in the Query Log and are not counted in the total limit. + +## How to set it up + +### Allowed clients + +This setting allows you to specify which clients can use your DNS server. It has the highest priority. For example, if the same IP address is on both the denied and allowed list, it will still be allowed. + +### Disallowed clients + +Here you can list the clients that are not allowed to use your DNS server. You can block access to all clients and use only selected ones. To do this, add two addresses to the disallowed clients: `0.0.0.0.0/0` and `::/0`. Then, in the *Allowed clients* field, specify the addresses that can access your server. + +:::note Important + +Before applying the access settings, make sure you're not blocking your own IP address. If you do, you won't be able to access the network. If that happens, just disconnect from the DNS server, go to the access settings, and adjust the configurations accordingly. + +::: + +### Disallowed domains + +Here you can specify the domains (as well as wildcard and DNS filtering rules) that will be denied access to your DNS server. + +![Access settings *border](https://cdn.adtidy.org/content/release_notes/dns/v2-5/AS-en.png) + +To display IP addresses associated with DNS requests in the Query log, select the *Log IP addresses* checkbox. To do this, open *Server settings* → *Advanced settings*. diff --git a/docs/private-dns/server-and-settings/advanced.md b/docs/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/docs/private-dns/server-and-settings/advanced.md @@ -0,0 +1,31 @@ +--- +title: Advanced settings +sidebar_position: 2 +--- + +The Advanced settings section is intended for the more experienced user and includes the following settings. + +## Respond to blocked domains + +Here you can select the DNS response for the blocked request: + +- **Default**: Respond with zero IP address (0.0.0.0 for A; :: for AAAA) when blocked by Adblock-style rule; respond with the IP address specified in the rule when blocked by /etc/hosts-style rule +- **REFUSED**: Respond with REFUSED code +- **NXDOMAIN**: Respond with NXDOMAIN code +- **Custom IP**: Respond with a manually set IP address + +## TTL (Time-To-Live) + +Time-to-live (TTL) sets the time period (in seconds) for a client device to cache the response to a DNS request and retrieve it from its cache without re-requesting the DNS server. If the TTL value is high, recently unblocked requests may still look blocked for a while. If TTL is 0, the device does not cache responses. + +## Block access to iCloud Private Relay + +Devices that use iCloud Private Relay may ignore their DNS settings, so AdGuard DNS cannot protect them. + +## Block Firefox canary domain + +Prevents Firefox from switching to the DoH resolver from its settings when AdGuard DNS is configured system-wide. + +## Log IP addresses + +By default, AdGuard DNS doesn’t log IP addresses of incoming DNS requests. If you enable this setting, IP addresses will be logged and displayed in Query log. diff --git a/docs/private-dns/server-and-settings/server-and-settings.md b/docs/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..f8608ec77 --- /dev/null +++ b/docs/private-dns/server-and-settings/server-and-settings.md @@ -0,0 +1,27 @@ +--- +title: Server and settings +sidebar_position: 1 +--- + +## What is server and how to use it + +When you set up Private AdGuard DNS, you'll encounter the term *servers*. + +A server acts as the “profile” that you connect your devices to. + +Servers include configurations that you can customize to your liking. + +Upon creating an account, we automatically establish a server with default settings. You can choose to modify this server or create a new one. + +For instance, you can have: + +- A server that allows all requests +- A server that blocks adult content and certain services +- A server that blocks adult content only during specific hours you choose + +For more information on traffic filtering and blocking rules, check out the article [“How to set up filtering in AdGuard DNS”](/private-dns/setting-up-filtering/blocklists.md). + +If you're interested in specific settings, there are dedicated articles available for that: + +- [Advanced settings](/private-dns/server-and-settings/advanced.md) +- [Access settings](/private-dns/server-and-settings/access.md) diff --git a/docs/private-dns/setting-up-filtering/_category_.json b/docs/private-dns/setting-up-filtering/_category_.json new file mode 100644 index 000000000..c97383588 --- /dev/null +++ b/docs/private-dns/setting-up-filtering/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 4, + "label": "How to set up filtering", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/setting-up-filtering/blocklists.md b/docs/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..c13924d93 --- /dev/null +++ b/docs/private-dns/setting-up-filtering/blocklists.md @@ -0,0 +1,65 @@ +--- +title: Blocklists +sidebar_position: 1 +--- + +## What blocklists are + +Blocklists are sets of rules in text format that AdGuard DNS uses to filter out ads and content that could compromise your privacy. In general, a filter consists of rules with a similar focus. For example, there may be rules for website languages (such as German or Russian filters) or rules that protect against phishing sites (such as the Phishing URL Blocklist). You can easily enable or disable these rules as a group. + +## Why they are useful + +Blocklists are designed for flexible customization of filtering rules. For example, you may want to block advertising domains in a specific language region, or you may want to get rid of tracking or advertising domains. Select the blocklists you want and customize the filtering to your liking. + +## How to activate blocklists in AdGuard DNS + +To activate the blocklists: + +1. Open the Dashboard. +1. Go to the *Servers* section. +1. Select the required server. +1. Click *Blocklists*. + +## Blocklists types + +### General + +A group of filters that includes lists for blocking ads and tracking domains. + +![General blocklists *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/blocklists/general.png) + +### Regional + +A group of filters consisting of regional lists to block domains in specific languages. + +![Regional blocklists *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/blocklists/regional.png) + +### Security + +A group of filters containing rules for blocking fraudulent sites and phishing domains. + +![Security blocklists *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/blocklists/security.png) + +### Other + +Blocklists with various blocking rules from third-party developers. + +![Other blocklists *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/blocklists/other.png) + +## Adding filters + +If you would like the list of AdGuard DNS filters to be expanded, you can submit a request to add them in the relevant section of [Hostlistsregistry](https://github.com/AdguardTeam/HostlistsRegistry) on GitHub. + +To submit a request: + +1. Go to the link above (you may need to register on GitHub). +1. Click *New issue*. +1. Click *Blocklist request* and fill out the form. +1. After filling out the form, click *Submit new issue*. + +If your filter's blocking rules do not duplicate duplicate the existing lists, it will be added to the repository. + +## User rules + +You can also create your own blocking rules. +Learn more in the [User rules article](/private-dns/setting-up-filtering/user-rules.md). diff --git a/docs/private-dns/setting-up-filtering/parental-control.md b/docs/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..a031472c9 --- /dev/null +++ b/docs/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Parental control +sidebar_position: 4 +--- + +## What is it + +Parental control is a set of settings that gives you the flexibility to customize access to certain websites with "sensitive" content. You can use this feature to restrict your children's access to adult sites, customize search queries, block the use of popular services, and more. + +## How to set it up + +You can flexibly configure all features on your servers, including the parental control feature. [In the corresponding article](private-dns/server-and-settings/server-and-settings.md), you can familiarize yourself with what a "server" is in AdGuard DNS and learn how to create different servers with different sets of settings. + +Then, go to the settings of the selected server and enable the required configurations. + +### Block adult websites + +Blocks websites with inappropriate and adult content. + +![Blocked website *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/parental_control/adult_blocked.png) + +### Safe search + +Removes inappropriate results from Google, Bing, DuckDuckGo, Yandex, Pixabay, Brave, and Ecosia. + +![Safe search *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/parental_control/porn.png) + +### YouTube restricted mode + +Removes the option to view and post comments under videos and interact with 18+ content on YouTube. + +![Restricted mode *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/parental_control/restricted.png) + +### Blocked services and websites + +AdGuard DNS blocks access to popular services with one click. It's useful if you don't want connected devices to visit Instagram and Youtube, for example. + +![Blocked services *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/parental_control/blocked_services.png) + +### Schedule off time + +Enables parental controls on selected days with a specified time interval. For example, you may have allowed your child to watch Youtube videos only until 23:00 on weekdays. But on weekends, this access is not restricted. Customize the schedule to your liking and block access to selected sites during the hours you want. + +![Schedule *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/parental_control/schedule.png) diff --git a/docs/private-dns/setting-up-filtering/security-features.md b/docs/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/docs/private-dns/setting-up-filtering/security-features.md @@ -0,0 +1,24 @@ +--- +title: Security features +sidebar_position: 3 +--- + +The AdGuard DNS security settings are a set of configurations designed to protect the user's personal information. + +Here you can choose which methods you want to use to protect yourself from attackers. This will protect you from visiting phishing and fake websites, as well as from potential leaks of sensitive data. + +### Block malicious, phishing, and scam domains + +To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. + +### Block newly registered domains + +Scammers often use recently registered domains for phishing and fraudulent schemes. For this reason, we have developed a special filter that detects the lifetime of a domain and blocks it if it was created recently. +Sometimes this can cause false positives, but statistics show that in most cases this setting still protects our users from losing confidential data. + +### Blocki malicious domains using blocklists + +AdGuard DNS supports adding third-party blocking filters. +Activate filters marked `security` for additional protection. + +To learn more about Blocklists [see separate article](/private-dns/setting-up-filtering/blocklists.md). diff --git a/docs/private-dns/setting-up-filtering/user-rules.md b/docs/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..8fde56008 --- /dev/null +++ b/docs/private-dns/setting-up-filtering/user-rules.md @@ -0,0 +1,30 @@ +--- +title: User rules +sidebar_position: 2 +--- + +## What is it and why you need it + +User rules are the same filtering rules as those used in common blocklists. You can customize website filtering to suit your needs by adding rules manually or importing them from a predefined list. + +To make your filtering more flexible and better suited to your preferences, check out the [rule syntax](/general/dns-filtering-syntax/) for AdGuard DNS filtering rules. + +## How to use + +To set up user rules: + +1. Navigate to the *Dashboard*. + +1. Go to the *Servers* section. + +1. Select the required server. + +1. Click the *User rules* option. + +1. You'll find several options for adding user rules. + + - The easiest way is to use the generator. To use it, click *Add new rule* → Enter the name of the domain you want to block or unblock → Click *Add rule* + ![Add rule *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/userrules_step5.png) + - The advanced way is to use the rule editor. Click *Open editor* and enter blocking rules according to [syntax](/general/dns-filtering-syntax/) + +This feature allows you to [redirect a query to another domain by replacing the contents of the DNS query](/general/dns-filtering-syntax/#dnsrewrite-modifier). diff --git a/docs/private-dns/solving-problems/_category_.json b/docs/private-dns/solving-problems/_category_.json index f5984a1c8..38a234d12 100644 --- a/docs/private-dns/solving-problems/_category_.json +++ b/docs/private-dns/solving-problems/_category_.json @@ -1,5 +1,5 @@ { - "position": 3, + "position": 7, "label": "Solving problems", "collapsible": true, "collapsed": true diff --git a/docs/private-dns/statistics-and-log/_category_.json b/docs/private-dns/statistics-and-log/_category_.json new file mode 100644 index 000000000..e93c5b380 --- /dev/null +++ b/docs/private-dns/statistics-and-log/_category_.json @@ -0,0 +1,6 @@ +{ + "position": 5, + "label": "Statistics and Query log", + "collapsible": true, + "collapsed": true +} \ No newline at end of file diff --git a/docs/private-dns/statistics-and-log/companies.md b/docs/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..84f291e75 --- /dev/null +++ b/docs/private-dns/statistics-and-log/companies.md @@ -0,0 +1,27 @@ +--- +title: Companies +sidebar_position: 4 +--- + +This tab allows you to quickly see which companies send the most requests and which companies have the most blocked requests. + +![Companies *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/companies.png) + +The Companies page is divided into two categories: + +- **Top requested company** +- **Top blocked company** + +These are further divided into sub-categories: + +- **Advertising**: advertising and other ad-related requests that collect and share user data, analyze user behavior, and target ads +- **Trackers**: requests from websites and third parties for the purpose of tracking user activity +- **Social media**: requests to social network websites +- **CDN**: request connected to Content Delivery Network (CDN), a worldwide network of proxy servers that speeds the delivery of content to end users +- **Other** + +### Top companies + +In this table, we not only show the names of the most visited or most blocked companies, but also display information about which domains are being requested from or which domains are being blocked the most. + +![Top companies *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/top_companies_breakdown.png) diff --git a/docs/private-dns/statistics-and-log/query-log.md b/docs/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..4dea03b84 --- /dev/null +++ b/docs/private-dns/statistics-and-log/query-log.md @@ -0,0 +1,36 @@ +--- +title: Query log +sidebar_position: 5 +--- + +## What is Query log + +Query log is a useful tool for working with AdGuard DNS. + +It allows you to view all requests made by your devices during the selected time period and sort requests by status, type, company, device, country. + +## How to use it + +Here's what you can see and what you can do in the *Query log*. + +### Detailed information on requests + +![Requests info *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/detailed_info.png) + +### Blocking and unblocking domains + +Requests can be blocked and unblocked without leaving the log, using the available tools. + +![Unblock domain *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/unblock_domain.png) + +### Sorting requests + +You can select the status of the request, its type, company, device, and the time period of the request you are interested in. + +![Sorting requests *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/query_sorted.png) + +### Disabling query logging + +If you wish, you can completely disable logging in the account settings (but remember that this will also disable statistics). + +![Logging *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/logging.png) diff --git a/docs/private-dns/statistics-and-log/statistics-and-log.md b/docs/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/docs/private-dns/statistics-and-log/statistics-and-log.md @@ -0,0 +1,13 @@ +--- +title: Statistics and Query log +sidebar_position: 1 +--- + +One of the purposes of using AdGuard DNS is to have a clear understanding of what your devices are doing and what they are connecting to. Without this clarity, there's no way to monitor the activity of your devices. + +AdGuard DNS provides a wide range of useful tools for monitoring queries: + +- [Statistics](/private-dns/statistics-and-log/statistics.md) +- [Traffic destination](/private-dns/statistics-and-log/traffic-destination.md) +- [Companies](/private-dns/statistics-and-log/companies.md) +- [Query log](/private-dns/statistics-and-log/query-log.md) diff --git a/docs/private-dns/statistics-and-log/statistics.md b/docs/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..179f1c77d --- /dev/null +++ b/docs/private-dns/statistics-and-log/statistics.md @@ -0,0 +1,55 @@ +--- +title: Statistics +sidebar_position: 2 +--- + +## General statistics + +The *Statistics* tab displays all summary statistics of DNS requests made by devices connected to the Private AdGuard DNS. It shows the total number and location of requests, the number of blocked requests, the list of companies to which the requests were directed, the types of requests, and the most frequently requested domains. + +![Blocked website *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/overall_stats.png) + +## Categories + +### Requests types + +- **Advertising**: advertising and other ad-related requests that collect and share user data, analyze user behavior, and target ads +- **Trackers**: requests from websites and third parties for the purpose of tracking user activity +- **Social media**: requests to social network websites +- **CDN**: request connected to Content Delivery Network (CDN), a worldwide network of proxy servers that speeds the delivery of content to end users +- **Other** + +![Request types *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/request_types.png) + +### Top companies + +Here you can see the companies that have sent the most requests. + +![Top companies *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/top_companies.png) + +### Top destinations + +This shows the countries to which the most requests have been sent. + +In addition to the country names, the list contains two more general categories: + +- **Not applicable**: Response doesn't include IP address +- **Unknown destination**: Country can't be determined from IP address + +![Top destinations *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/top_destinations.png) + +### Top domains + +Contains a list of domains that have been sent the most requests. + +![Top domains *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/top_domains.png) + +### Encrypted requests + +Shows the total number of requests and the percentage of encrypted and unencrypted traffic. + +![Encrypted requests *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/encrypted_requests.png) + +### Top clients + +Displays the number of requests made to clients. To view client IP addresses, enable the *Log IP addresses* option in the *Server settings*. [More about server settings](/private-dns/server-and-settings/advanced.md) can be found in a related section. diff --git a/docs/private-dns/statistics-and-log/traffic-destination.md b/docs/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..9b7e01900 --- /dev/null +++ b/docs/private-dns/statistics-and-log/traffic-destination.md @@ -0,0 +1,8 @@ +--- +title: Traffic destination +sidebar_position: 3 +--- + +This feature shows where DNS requests sent by your devices are routed. In addition to viewing a map of request destinations, you can filter the information by date, device, and country. + +![Traffic destination *border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/statistics/traffic_destination.png)