diff --git a/i18n/cs/docusaurus-plugin-content-docs/current.json b/i18n/cs/docusaurus-plugin-content-docs/current.json index 1974bf3f8..3d9957bff 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current.json +++ b/i18n/cs/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "Klient AdGuard DNS", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routery", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/dns-providers.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/dns-providers.md index 7de959f7a..68dc78433 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/dns-providers.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/dns-providers.md @@ -389,12 +389,12 @@ Tyto servery používají některé záznamy, samopodepsané certifikáty nebo n ### DNSPod Public DNS+ -[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) is a privacy-friendly DNS provider with years of experience in domain name resolution services development, it aims to provide users more rapid, accurate and stable recursive resolution service. +[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) je poskytovatel DNS šetrný k soukromí, který má dlouholeté zkušenosti s vývojem služeb pro překlad názvů domén a jehož cílem je poskytovat uživatelům rychlejší, přesnější a stabilnější služby rekurzivního překladu. | Protokol | Adresa | | | -------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS, IPv4 | `119.29.29.29` | [Přidat do AdGuardu](adguard:add_dns_server?address=119.29.29.29&name=), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=119.29.29.29&name=) | -| DNS, IPv6 | `2402:4e00::` | [Add to AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | +| DNS, IPv6 | `2402:4e00::` | [Přidat do AdGuardu](adguard:add_dns_server?address=2402:4e00::&name=), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | | DNS-over-HTTPS | `https://dns.pub/dns-query` | [Přidat do AdGuardu](adguard:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub) | | DNS-over-TLS | `tls://dot.pub` | [Přidat do AdGuardu](adguard:add_dns_server?address=tls://dot.pub&name=dot.pub), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=tls://dot.pub&name=dot.pub) | @@ -838,7 +838,7 @@ Servery [Restena DNS](https://www.restena.lu/en/service/public-dns-resolver) pos | Protokol | Adresa | | | -------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | DNS-over-HTTPS | `https://kaitain.restena.lu/dns-query` IP: `158.64.1.29` a IPv6: `2001:a18:1::29` | [Přidat do AdGuardu](adguard:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu) | -| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` and IPv6: `2001:a18:1::29` | [Add to AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | +| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` a IPv6: `2001:a18:1::29` | [Přidat do AdGuardu](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Přidat do AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | ### 114DNS diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..6f85cec39 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Klikněte na _Síť_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..b5adfb8a7 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. Klikněte na _Uložit_. + +## 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. Klikněte na _Uložit_. + +## 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..5e6d7b6b6 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Routery +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..37bd9e6d4 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Klikněte na _Uložit_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..458432fdd --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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. Otevřete předvolby routeru. 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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/overview.md index 08596ed6a..df54ac143 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,154 +38,179 @@ Zde je jednoduché srovnání funkcí dostupných ve veřejném a soukromém AdG | - | Podrobný záznam dotazů | | - | Rodičovská ochrana | -## Jak nastavit soukromý AdGuard DNS -### Pro zařízení podporující DoH, DoT a DoQ + + +### 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..19c638fb3 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md @@ -0,0 +1,32 @@ +--- +title: Nastavení přístupu +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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..b53ed4ff7 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Obecné + +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) + +### Další + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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. + +## Uživatelská pravidla + +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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..58dc68def --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Rodičovská ochrana +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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..42458402b --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md @@ -0,0 +1,30 @@ +--- +title: Uživatelská pravidla +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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e12682d71 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md @@ -0,0 +1,36 @@ +--- +title: Protokol dotazů +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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..cdf7e5ac0 --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md @@ -0,0 +1,55 @@ +--- +title: Statistiky +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/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..fba81bcbc --- /dev/null +++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md @@ -0,0 +1,8 @@ +--- +title: Cíl datového provozu +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) diff --git a/i18n/da/docusaurus-plugin-content-docs/current.json b/i18n/da/docusaurus-plugin-content-docs/current.json index b52a02bee..c6c712095 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current.json +++ b/i18n/da/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS-klient", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routere", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/dns-providers.md b/i18n/da/docusaurus-plugin-content-docs/current/general/dns-providers.md index 3239ce0da..da77a7206 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/dns-providers.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/dns-providers.md @@ -389,12 +389,12 @@ Disse servere bruger noget logning, selvsignerede certifikater eller ingen under ### DNSPod Public DNS+ -[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) is a privacy-friendly DNS provider with years of experience in domain name resolution services development, it aims to provide users more rapid, accurate and stable recursive resolution service. +[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) er en fortrolighedsvenlig DNS-udbyder med mange års erfaring inden for udvikling af domænenavnsopløsningstjenester, hvis formål er at give brugerne en hurtigere, mere præcis og stabil rekursiv opløsningstjeneste. | Protokol | Adresse | | | -------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS, IPv4 | `119.29.29.29` | [Føj til AdGuard](adguard:add_dns_server?address=119.29.29.29&name=), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=119.29.29.29&name=) | -| DNS, IPv6 | `2402:4e00::` | [Add to AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | +| DNS, IPv6 | `2402:4e00::` | [Føj til AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | | DNS-over-HTTPS | `https://dns.pub/dns-query` | [Føj til AdGuard](adguard:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub) | | DNS-over-TLS | `tls://dot.pub` | [Føj til AdGuard](adguard:add_dns_server?address=tls://dot.pub&name=dot.pub), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=tls://dot.pub&name=dot.pub) | @@ -838,7 +838,7 @@ I tilstanden "Family", Beskyttet + blokering af voksenindhold. | Protokol | Adresse | | | -------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS-over-HTTPS | `https://kaitain.restena.lu/dns-query` IP: `158.64.1.29` og IPv6: `2001:a18:1::29` | [Føj til AdGuard](adguard:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu) | -| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` and IPv6: `2001:a18:1::29` | [Add to AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | +| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` og IPv6: `2001:a18:1::29` | [Føj til AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Føj til AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | ### 114DNS diff --git a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..988e01797 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Klik på _Netværk_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..fe812c879 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. Klik på _Gem_. + +## 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. Klik på _Gem_. + +## 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..afa20247e --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Routere +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..11eef97b0 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Klik på _Gem_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..8724c691a --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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. Åbn præferencerne for routeren. 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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/overview.md index 57ba3fc4e..4dd3b44a6 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,154 +38,179 @@ Her er en simpel funktionssammenligning mellem Public og Private AdGuard DNS. | - | Detaljeret forespørgselslog | | - | Forældrekontrol | -## Sådan opsættes Private AdGuard DNS -### Til enheder, som understøtter DoH, DoT og DoQ + + +### 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..65ac48ad1 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md @@ -0,0 +1,32 @@ +--- +title: Adgangsindstillinger +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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..06af642c8 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Generelt + +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) + +### Sikkerhed + +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) + +### Øvrigt + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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. + +## Brugerregler + +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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f88580e59 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Forældrekontrol +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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..25a88a0e3 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md @@ -0,0 +1,30 @@ +--- +title: Brugerregler +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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..9fa1c43be --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md @@ -0,0 +1,36 @@ +--- +title: Forespørgselslog +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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..5e223063c --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md @@ -0,0 +1,55 @@ +--- +title: Statistikker +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/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..53489e02a --- /dev/null +++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md @@ -0,0 +1,8 @@ +--- +title: Trafikdestination +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) diff --git a/i18n/de/docusaurus-plugin-content-docs/current.json b/i18n/de/docusaurus-plugin-content-docs/current.json index 5264a27ed..76a34e20a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current.json +++ b/i18n/de/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5b0539282..5b763d450 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..1da52e9e1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Allgemein + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/en/docusaurus-plugin-content-docs/current.json +++ b/i18n/en/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/es/docusaurus-plugin-content-docs/current.json b/i18n/es/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..757a31c37 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current.json +++ b/i18n/es/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Roteadores", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md index 5ac32c043..b54292af1 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md @@ -156,7 +156,7 @@ To update AdGuard Home package without the need to use Web API run: This setup will automatically cover all devices connected to your home router, and you won’t need to configure each of them manually. -1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as http://192.168.0.1/ or http://192.168.1.1/. You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. +1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as or . You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. 2. Find the DHCP/DNS settings. Look for the DNS letters next to a field that allows two or three sets of numbers, each divided into four groups of one to three digits. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..63f7607fe --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Roteadores +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/overview.md index ca486bd5f..e8679b08a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ Here is a simple comparison of features available in public and private AdGuard | - | Registro de consultas detallado | | - | Control parental | -## 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..2dced35c3 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Control parental +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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/es/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current.json b/i18n/fi/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current.json +++ b/i18n/fi/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5f56d0e58..2b6ea2589 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/fi/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current.json b/i18n/fr/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current.json +++ b/i18n/fr/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/overview.md index c67db8787..174768d35 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ Here is a simple comparison of features available in public and private AdGuard | - | Journal de requêtes détaillé | | - | Contrôle Parental | -## 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..19ad31192 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Contrôle Parental +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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current.json b/i18n/hr/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current.json +++ b/i18n/hr/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5f56d0e58..2b6ea2589 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/hr/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/it/docusaurus-plugin-content-docs/current.json b/i18n/it/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current.json +++ b/i18n/it/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md index 5ac32c043..b54292af1 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md @@ -156,7 +156,7 @@ To update AdGuard Home package without the need to use Web API run: This setup will automatically cover all devices connected to your home router, and you won’t need to configure each of them manually. -1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as http://192.168.0.1/ or http://192.168.1.1/. You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. +1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as or . You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. 2. Find the DHCP/DNS settings. Look for the DNS letters next to a field that allows two or three sets of numbers, each divided into four groups of one to three digits. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/overview.md index c7736c715..9cb1293c7 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/it/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current.json b/i18n/ja/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current.json +++ b/i18n/ja/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/overview.md index c96f775a3..8b260e102 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current.json b/i18n/ko/docusaurus-plugin-content-docs/current.json index 8656c3785..78c18742b 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current.json +++ b/i18n/ko/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/overview.md index 2df497854..0d5234abb 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/ko/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current.json b/i18n/nl/docusaurus-plugin-content-docs/current.json index 3fcdee72c..546c72c77 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current.json +++ b/i18n/nl/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/dns-providers.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/dns-providers.md index dbf8885cb..395adc386 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/dns-providers.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/dns-providers.md @@ -389,12 +389,12 @@ These servers use some logging, self-signed certs or no support for strict mode. ### DNSPod Public DNS+ -[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) is a privacy-friendly DNS provider with years of experience in domain name resolution services development, it aims to provide users more rapid, accurate and stable recursive resolution service. +[DNSPod Public DNS+](https://www.dnspod.cn/products/publicdns) is een privacyvriendelijke DNS-provider met jarenlange ervaring in de ontwikkeling van domeinnaamresolutieservices. Het doel is om gebruikers een snellere, nauwkeurigere en stabielere recursieve resolutieservice te bieden. | Protocol | Adres | | | -------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS, IPv4 | `119.29.29.29` | [Add to AdGuard](adguard:add_dns_server?address=119.29.29.29&name=), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=119.29.29.29&name=) | -| DNS, IPv6 | `2402:4e00::` | [Add to AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | +| DNS, IPv6 | `2402:4e00::` | [Toevoegen aan AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Toevoegen aan AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | | DNS-over-HTTPS | `https://dns.pub/dns-query` | [Add to AdGuard](adguard:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub) | | DNS-over-TLS | `tls://dot.pub` | [Add to AdGuard](adguard:add_dns_server?address=tls://dot.pub&name=dot.pub), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=tls://dot.pub&name=dot.pub) | @@ -838,7 +838,7 @@ In "Family" mode, Protected + blocking adult content. | Protocol | Adres | | | -------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS-over-HTTPS | `https://kaitain.restena.lu/dns-query` IP: `158.64.1.29` and IPv6: `2001:a18:1::29` | [Add to AdGuard](adguard:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu) | -| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` and IPv6: `2001:a18:1::29` | [Add to AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | +| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` en IPv6: `2001:a18:1::29` | [Toevoegen aan AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Toevoegen aan AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | ### 114DNS @@ -1071,7 +1071,7 @@ Blocks more ads and malware than AdGuard DNS thanks to more advanced syntax, but | DNS-over-QUIC | `quic://dandelionsprout.asuscomm.com:48582` | [Add to AdGuard](adguard:add_dns_server?address=quic://dandelionsprout.asuscomm.com:48582&name=dandelionsprout.asuscomm.com:48582), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=quic://dandelionsprout.asuscomm.com:48582&name=dandelionsprout.asuscomm.com:48582) | | DNS, IPv4 | Varies; see link above. | | | DNS, IPv6 | Varies; see link above. | | -| DNSCrypt, IPv4 | Varies; see link above. | | +| DNSCrypt, IPv4 | Varieert; zie bovenstaande link. | | ### DNS Forge diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/overview.md index 839757569..a10101fe5 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,12 +38,13 @@ Hier is een eenvoudige vergelijking van functies die beschikbaar zijn in openbar | - | Detailed query log | | - | Parental control | -## Hoe je privé AdGuard DNS instelt -### Voor apparaten die DoH, DoT en DoQ ondersteunen + + +### 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..37b76da99 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Algemeen + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/nl/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current.json b/i18n/pt-BR/docusaurus-plugin-content-docs/current.json index 5c4bddd50..5b7131177 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current.json +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Roteadores", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..63f7607fe --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Roteadores +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/overview.md index d11b05e6e..5a3f67b92 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ Here is a simple comparison of features available in public and private AdGuard | - | Registro de consulta detalhado | | - | Controle parental | -## 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..6ad66a911 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Geral + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..b5d18c57d --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Controle parental +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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current.json b/i18n/ru/docusaurus-plugin-content-docs/current.json index 17ee35a82..5f17522e7 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current.json +++ b/i18n/ru/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Роутеры", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..301955f65 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Нажмите _Сеть_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..693d3e439 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. Нажмите _Сохранить_. + +## 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. Нажмите _Сохранить_. + +## 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..7f817c6c3 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Роутеры +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..2229ef157 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Нажмите _Сохранить_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..be99c1cc6 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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. Откройте настройки вашего роутера. 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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/overview.md index 2491c3b61..797151c33 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,154 +38,179 @@ sidebar_position: 1 | - | Подробный журнал запросов | | - | Родительский контроль | -## Как настроить личный AdGuard DNS -### Для устройств, поддерживающих DoH, DoT и DoQ + + +### 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..e7ce4a6c9 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md @@ -0,0 +1,32 @@ +--- +title: Настройки доступа +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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..36e831b10 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Общее + +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) + +### Безопасность + +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) + +### Другие + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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. + +## Пользовательские правила + +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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..ed4da9e57 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Родительский контроль +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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..fb29ca1fc --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md @@ -0,0 +1,30 @@ +--- +title: Пользовательские правила +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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..b5d174be6 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md @@ -0,0 +1,36 @@ +--- +title: Журнал запросов +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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..017209b90 --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md @@ -0,0 +1,55 @@ +--- +title: Статистика +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/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..dbe57bd0a --- /dev/null +++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md @@ -0,0 +1,8 @@ +--- +title: Назначение трафика +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) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current.json b/i18n/sk/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current.json +++ b/i18n/sk/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5f56d0e58..2b6ea2589 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/sk/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current.json b/i18n/sl/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current.json +++ b/i18n/sl/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md index 5ac32c043..b54292af1 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md @@ -156,7 +156,7 @@ To update AdGuard Home package without the need to use Web API run: This setup will automatically cover all devices connected to your home router, and you won’t need to configure each of them manually. -1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as http://192.168.0.1/ or http://192.168.1.1/. You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. +1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as or . You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. 2. Find the DHCP/DNS settings. Look for the DNS letters next to a field that allows two or three sets of numbers, each divided into four groups of one to three digits. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5f56d0e58..2b6ea2589 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/sl/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/sr/docusaurus-plugin-content-docs/current.json b/i18n/sr/docusaurus-plugin-content-docs/current.json index 23ca57663..328f6309d 100644 --- a/i18n/sr/docusaurus-plugin-content-docs/current.json +++ b/i18n/sr/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/overview.md index e5ba76754..35ba17096 100644 --- a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..ec0fab6e7 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Opšte + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/sr/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current.json b/i18n/tr/docusaurus-plugin-content-docs/current.json index a4f893c33..11847d34f 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current.json +++ b/i18n/tr/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS İstemcisi", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Yönlendiriciler", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/dns-providers.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/dns-providers.md index e74927afd..47302acb5 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/dns-providers.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/dns-providers.md @@ -394,7 +394,7 @@ Bu sunucular bazı günlük kaydı, kendinden imzalı sertifikalar kullanır vey | Protokol | Adres | | | -------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS, IPv4 | `119.29.29.29` | [AdGuard'a ekle](adguard:add_dns_server?address=119.29.29.29&name=), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=119.29.29.29&name=) | -| DNS, IPv6 | `2402:4e00::` | [Add to AdGuard](adguard:add_dns_server?address=2402:4e00::&name=), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=2402:4e00::&name=) | +| DNS, IPv6 | `2402:4e00::` | [AdGuard'a ekle](adguard:add_dns_server?address=2402:4e00::&name=), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=2402:4e00::&name=) | | DNS-over-HTTPS | `https://dns.pub/dns-query` | [AdGuard'a ekle](adguard:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=https://dns.pub/dns-query&name=dns.pub) | | DNS-over-TLS | `tls://dot.pub` | [AdGuard'a ekle](adguard:add_dns_server?address=tls://dot.pub&name=dot.pub), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=tls://dot.pub&name=dot.pub) | @@ -838,7 +838,7 @@ ByteDance Public DNS, Çin'de ByteDance tarafından sunulan ücretsiz bir altern | Protokol | Adres | | | -------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS-over-HTTPS | `https://kaitain.restena.lu/dns-query` IP: `158.64.1.29` ve IPv6: `2001:a18:1::29` | [AdGuard'a ekle](adguard:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=https://kaitain.restena.lu/dns-query&name=kaitain.restena.lu) | -| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` and IPv6: `2001:a18:1::29` | [Add to AdGuard](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [Add to AdGuard VPN](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | +| DNS-over-TLS | `tls://kaitain.restena.lu` IP: `158.64.1.29` ve IPv6: `2001:a18:1::29` | [AdGuard'a ekle](adguard:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu), [AdGuard VPN'e ekle](adguardvpn:add_dns_server?address=tls://kaitain.restena.lu&name=kaitain.restena.lu) | ### 114DNS diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..6c90d72fc --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. _Ağ_ öğesine tıklayın. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..94cd79057 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. _Kaydet_ öğesine tıklayın. + +## 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. _Kaydet_ öğesine tıklayın. + +## 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..f0a4c37fe --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md @@ -0,0 +1,26 @@ +--- +title: Yönlendiriciler +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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..61259ee23 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. _Kaydet_ öğesine tıklayın. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..457772022 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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. Yönlendiricinizin tercihlerini açın. 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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/overview.md index a2938b87b..00e0b1c53 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,154 +38,179 @@ Burada genel ve özel AdGuard DNS'de bulunan özelliklerin basit bir karşılaş | - | Ayrıntılı sorgu günlüğü | | - | Ebeveyn denetimi | -## Özel AdGuard DNS nasıl kurulur -### DoH, DoT ve DoQ'yu destekleyen cihazlar için + + +### 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..b86795678 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md @@ -0,0 +1,32 @@ +--- +title: Erişim ayarları +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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..dff8fd638 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. Click _Blocklists_. + +## Blocklists types + +### Genel + +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) + +### Diğer + +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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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. + +## Kullanıcı kuralları + +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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..48eaf6cda --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: Ebeveyn denetimi +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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..3f3e64238 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md @@ -0,0 +1,30 @@ +--- +title: Kullanıcı kuralları +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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e294d1ba5 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md @@ -0,0 +1,36 @@ +--- +title: Sorgu günlüğü +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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..89394e048 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md @@ -0,0 +1,55 @@ +--- +title: İstatistikler +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/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..efdba44b5 --- /dev/null +++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md @@ -0,0 +1,8 @@ +--- +title: Trafik istikameti +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) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current.json b/i18n/vi/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current.json +++ b/i18n/vi/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/overview.md index 6594f6e33..5c671a747 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/vi/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current.json b/i18n/zh-CN/docusaurus-plugin-content-docs/current.json index 817e7c881..a748d930b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md index 5ac32c043..b54292af1 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/getting-started.md @@ -156,7 +156,7 @@ To update AdGuard Home package without the need to use Web API run: This setup will automatically cover all devices connected to your home router, and you won’t need to configure each of them manually. -1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as http://192.168.0.1/ or http://192.168.1.1/. You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. +1. Open the preferences for your router. Usually, you can access it from your browser via a URL, such as or . You may be prompted to enter a password. If you don’t remember it, you can often reset the password by pressing a button on the router itself, but be aware that if this procedure is chosen, you will probably lose the entire router configuration. If your router requires an app to set it up, please install the app on your phone or PC and use it to access the router’s settings. 2. Find the DHCP/DNS settings. Look for the DNS letters next to a field that allows two or three sets of numbers, each divided into four groups of one to three digits. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/overview.md index 14bb17042..ad4535454 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ Here is a simple comparison of features available in public and private AdGuard | - | 详细的查询日志 | | - | 家长控制 | -## 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..0878c578a --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md @@ -0,0 +1,44 @@ +--- +title: 家长控制 +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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/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) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current.json b/i18n/zh-TW/docusaurus-plugin-content-docs/current.json index 1ac2c09cd..47272737b 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current.json +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current.json @@ -38,5 +38,37 @@ "sidebar.sidebar.category.AdGuard DNS Client": { "message": "AdGuard DNS Client", "description": "The label for category AdGuard DNS Client in sidebar sidebar" + }, + "sidebar.sidebar.category.How to connect devices": { + "message": "How to connect devices", + "description": "The label for category How to connect devices in sidebar sidebar" + }, + "sidebar.sidebar.category.Mobile and desktop": { + "message": "Mobile and desktop", + "description": "The label for category Mobile and desktop in sidebar sidebar" + }, + "sidebar.sidebar.category.Routers": { + "message": "Routers", + "description": "The label for category Routers in sidebar sidebar" + }, + "sidebar.sidebar.category.Game consoles": { + "message": "Game consoles", + "description": "The label for category Game consoles in sidebar sidebar" + }, + "sidebar.sidebar.category.Other options": { + "message": "Other options", + "description": "The label for category Other options in sidebar sidebar" + }, + "sidebar.sidebar.category.Server and settings": { + "message": "Server and settings", + "description": "The label for category Server and settings in sidebar sidebar" + }, + "sidebar.sidebar.category.How to set up filtering": { + "message": "How to set up filtering", + "description": "The label for category How to set up filtering in sidebar sidebar" + }, + "sidebar.sidebar.category.Statistics and Query log": { + "message": "Statistics and Query log", + "description": "The label for category Statistics and Query log in sidebar sidebar" } } diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/connect-devices.md new file mode 100644 index 000000000..9abff2ade --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/game-consoles.md new file mode 100644 index 000000000..b1caa95a4 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo-switch.md new file mode 100644 index 000000000..0059e101c --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Go to _System Settings_ → _Internet_. +3. Select the Wi-Fi network that you want to modify the DNS settings for. +4. Click _Change Settings_ for the selected Wi-Fi network. +5. Scroll down and select _DNS Settings_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/nintendo.md new file mode 100644 index 000000000..beded4821 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. Go to _Internet Settings_ → _Connection Settings_. +3. Select the connection file, then select _Change Settings_. +4. Select _DNS_ → _Set Up_. +5. Set _Auto-Obtain DNS_ to _No_. +6. Select _Detailed Setup_ → _Primary DNS_. Hold down the left arrow to delete the existing DNS. +7. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +8. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/playstation.md new file mode 100644 index 000000000..2630e1b10 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. From the home screen, select the gear icon located in the top row. +3. In the _Settings_ menu, select _Network_. +4. Select _Set Up Internet Connection_. +5. Choose _Use Wi-Fi_ or _Use a LAN Cable_, depending on your network setup. +6. Select _Custom_ and then select _Automatic_ for _IP Address Settings_. +7. For _DHCP Host Name_, select _Do Not Specify_. +8. For _DNS Settings_, select _Manual_. +9. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +10. Select _Next_ to continue. +11. On the _MTU Settings_ screen, select _Automatic_. +12. On the _Proxy Server_ screen, select _Do Not Use_. +13. Select _Test Internet Connection_ to test your new DNS settings. +14. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/steam.md new file mode 100644 index 000000000..a579a1267 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Click _Network_. +3. Click the gear icon next to the network connection you want to configure. +4. Select IPv4 or IPv6, depending on the type of network you're using. +5. Select _Automatic (DHCP) addresses only_ or _Automatic (DHCP)_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/game-consoles/xbox-one.md new file mode 100644 index 000000000..77975df23 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Press the Xbox button on your controller to open the guide, then select _System_ from the menu. +3. In the _Settings_ menu, select _Network_. +4. Under _Network Settings_, select _Advanced Settings_. +5. Under _DNS Settings_, select _Manual_. +6. In the _DNS Server_ field, enter one of the following DNS server addresses: + - `94.140.14.49` + - `94.140.14.59` +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/android.md new file mode 100644 index 000000000..2e933ff64 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Android. +3. 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. +2. Open the app. +3. 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) +4. Tap _DNS protection_. + ![DNS protection \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_ab/android_step5.png) +6. 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) +7. 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) +8. Tap _Add_. +9. 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) +10. 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. +2. Open the app. +3. 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) +4. Open _App settings_. + ![App settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step4.png) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/android_vpn/android_step5.png) +6. 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) +7. 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) +8. 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) +9. 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) +2. 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) +3. Select the _Private DNS provider hostname_ option and and enter the address of your personal server: `{Your_Device_ID}.d.adguard-dns.com`. +4. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/ios.md new file mode 100644 index 000000000..583d96684 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select iOS. +3. 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. +2. Open the AdGuard app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. 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. +2. Open the AdGuard VPN app. +3. 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) +4. Open _General_. + ![General settings \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step4.jpg) +5. Select _DNS server_. + ![DNS server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step5.png) +6. 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) +7. 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) +8. Tap _Save_. + ![Save server \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_vpn/ios_step8.jpg) +9. 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. +2. Open settings. +3. Tap _Profile Downloaded_. + ![Profile Downloaded \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/ios_manual/manual_step3.png) +4. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/linux.md new file mode 100644 index 000000000..15999da7b --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Linux. +3. 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/). +2. Access [settings](https://adguard-vpn.com/kb/adguard-vpn-for-linux/settings/). +3. To set a specific DNS server, use the command: `adguardvpn-cli config set-dns `, where `` is your private server’s address. +4. 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_. +2. Select the _Wireless_ tab, then choose the network you’re connected to. +3. Click _Edit_ → _IPv4_. +4. Change the listed DNS addresses to the following addresses: + - `94.140.14.49` + - `94.140.14.59` +5. Turn off _Auto mode_. +6. Click _Apply_. +7. Go to _IPv6_. +8. 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` +9. Turn off _Auto mode_. +10. Click _Apply_. +11. 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. +2. In the command line, type: `su`. +3. Enter your `admin` password. +4. In the command line, type: `nano /etc/resolv.conf`. +5. 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` +6. Press _Ctrl + O_ to save the document. +7. Press _Enter_. +8. Press _Ctrl + X_ to save the document. +9. In the command line, type: `/etc/init.d/networking restart`. +10. Press _Enter_. +11. Close the Terminal. +12. 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` + +2. 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}` + +3. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/macos.md new file mode 100644 index 000000000..3e3be5626 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Mac. +3. 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. +2. Open the app. +3. 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) +4. Select _Preferences..._. + ![Preferences \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step4.png) +5. 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) +6. 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) +7. Click _+_ in the bottom left corner. + ![Click + \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step7.png) +8. 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) +9. Click _Save and Choose_. + ![Save and Choose \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/mac_ab/mac_step9.png) +10. 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. +2. Open the AdGuard VPN app. +3. 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) +4. 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) +5. Click _Save and select_. +6. 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. +2. 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) +3. 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) +4. 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) +5. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/mobile-and-desktop/windows.md new file mode 100644 index 000000000..0855ffb23 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Windows. +3. 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. +2. Open the app. +3. 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) +4. 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) +5. 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) +6. 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) +7. 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) +8. Click _Save and select_. + ![Save and select \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_ab/windows_step8.png) +9. 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. +2. Open the app and click _Settings_. +3. Select _App settings_. + ![App settings \*border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/windows_vpn/windows_step4.png) +4. 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) +5. 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) +6. 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) +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/automatic-connection.md new file mode 100644 index 000000000..c182d330a --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Go to _Devices_. +3. 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_. +2. Select the protocol you want to use as well as the device name and the device type. +3. Click _Generate link_. + ![Generate link \*mobile\_border](https://cdn.adtidy.org/content/kb/dns/private/new_dns/connect/automatically_step7.png) +4. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/dedicated-ip.md new file mode 100644 index 000000000..3c5d33eff --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously created device. +3. Select _Use server addresses_. +4. Next, open _Plain DNS Server Addresses_. +5. Select the server you wish to use. +6. To bind a dedicated IPv4 address, click _Assign_. +7. 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) +8. Copy and paste the selected dedicated address into the device configurations. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/doh-authentication.md new file mode 100644 index 000000000..cddac5d2c --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Add a device or go to the settings of a previously created device. +3. Click _Use DNS server addresses_ and open the _Encrypted DNS server addresses_ section. +4. Configure DNS-over-HTTPS with authentication as you like. +5. Reconfigure your device to use this server in the AdGuard DNS Client or one of the AdGuard apps. +6. 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) +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/other-options/linked-ip.md new file mode 100644 index 000000000..2ad4f6285 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Add a new device or open the settings of a previously connected device. +3. Go to _Use DNS server addresses_. +4. 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) +2. 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. +3. Enter the domain in your router settings and sync the configurations. +4. Go to the Linked IP settings to connect the address, then navigate to _Advanced Settings_ and click _Configure DDNS_. +5. 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. +2. 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}'"` +3. 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`. +2. Add a task: + - Insert the following line: + `/5 * * * * curl https://linkip.adguard-dns.com/linkip/{ServerID}/{UniqueKey}` + - This job will run every 5 minutes +3. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/asus.md new file mode 100644 index 000000000..810269254 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/). +2. Enter the administrator username (usually, it’s admin) and router password. +3. In the _Advanced Settings_ sidebar, navigate to the WAN section. +4. In the _WAN DNS Settings_ section, set _Connect to DNS Server automatically_ to _No_. +5. Set _Forward local queries_, _Enable DNS Rebind_, and _Enable DNSSEC_ to _No_. +6. Change DNS Privacy Protocol to DNS-over-TLS (DoT). +7. Make sure the _DNS-over-TLS Profile_ is set to _Strict_. +8. 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` +9. For _TLS Port_, enter 853. +10. In the _TLS Hostname_ field, enter the Private AdGuard DNS server address: + - `{Your_Device_ID}.d.adguard-dns.com` +11. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_. +4. Select _WAN_ or _Internet_. +5. Open _DNS Settings_ or _DNS_. +6. 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` +7. Save the settings. +8. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/fritzbox.md new file mode 100644 index 000000000..2d92bcd77 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. Under DNS-over-TLS (DoT), check _Use DNS-over-TLS_ if supported by the provider. +6. Select _Use Custom TLS Server Name Indication (SNI)_ and enter the AdGuard Private DNS server address: `{Your_Device_ID}.d.adguard-dns.com`. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _DNS_ or _DNS Settings_. +5. 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` +6. Save the settings. +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/keenetic.md new file mode 100644 index 000000000..5139d1f0a --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `https://d.adguard-dns.com/dns-query/{Your_Device_ID}` field. +9. 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`. +2. Press the menu button at the bottom of the screen and select _Management_. +3. Open _System settings_. +4. Press _Component options_ → _System component options_. +5. In _Utilities and services_, select DNS-over-HTTPS proxy and install it. +6. Head to _Menu_ → _Network rules_ → _Internet safety_. +7. Navigate to DNS-over-HTTPS servers and click _Add DNS-over-HTTPS server_. +8. Enter the URL of the private AdGuard DNS server in the `tls://*********.d.adguard-dns.com` field. +9. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Internet_ or _Home Network_. +4. Select _WAN_ or _Internet_. +5. Select _DNS_ or _DNS Settings_. +6. 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` +7. Save the settings. +8. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/mikrotik.md new file mode 100644 index 000000000..cfb61f713 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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 +2. 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_ +3. 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_ +4. 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` +5. 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_ +6. Link your IP. +7. 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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Webfig_ → _IP_ → _DNS_. +4. 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` +5. Save the settings. +6. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md new file mode 100644 index 000000000..37b09c580 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/openwrt.md @@ -0,0 +1,95 @@ +--- +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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Network_ → _Interfaces_. +4. Select your Wi-Fi network or wired connection. +5. Scroll down to IPv4 address or IPv6 address, depending on the IP version you want to configure. +6. 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` +7. Optionally, you can enable DNS forwarding if you want the router to act as a DNS forwarder for devices on your network. +8. Save the settings. +9. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/opnsense.md new file mode 100644 index 000000000..911b2b0de --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Click _Services_ in the top menu, then select _DHCP Server_ from the drop-down menu. +4. On the _DHCP Server_ page, select the interface that you want to configure the DNS settings for (e.g., LAN, WLAN). +5. Scroll down to _DNS Servers_. +6. 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` +7. Save the settings. +8. Optionally, you can enable DNSSEC for enhanced security. +9. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/routers.md new file mode 100644 index 000000000..b7304537e --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. +2. In the drop-down menu _Device type_, select Router. +3. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/synology-nas.md new file mode 100644 index 000000000..7a287e167 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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`. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Control Panel_ or _Network_. +4. Select _Network Interface_ or _Network Settings_. +5. Select your Wi-Fi network or wired connection. +6. 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` +7. Save the settings. +8. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/unifi.md new file mode 100644 index 000000000..e41035812 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Go to _Settings_ → _Networks_. +3. Click _Edit Network_ → _WAN_. +4. 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` +5. Click _Save_. +6. Return to _Network_. +7. Choose _Edit Network_ → _LAN_. +8. Find _DHCP Name Server_ and select _Manual_. +9. 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` +10. Save the settings. +11. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md new file mode 100644 index 000000000..2ccbb5f78 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/universal.md @@ -0,0 +1,32 @@ +--- +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/) + +2. 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. + + ::: + +3. 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` + +4. Save the settings. + +5. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/connect-devices/routers/xiaomi.md new file mode 100644 index 000000000..e9ffed727 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Enter the administrator username (usually, it’s admin) and router password. +3. Open _Advanced Settings_ or _Advanced_, depending on your router model. +4. Open _Network_ or _Internet_ and look for DNS or DNS Settings. +5. 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` +6. Save the settings. +7. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/overview.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/overview.md index 5f56d0e58..2b6ea2589 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/overview.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/overview.md @@ -38,7 +38,8 @@ 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/access.md new file mode 100644 index 000000000..33842dbd0 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/advanced.md new file mode 100644 index 000000000..d4ec6378b --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/server-and-settings/server-and-settings.md new file mode 100644 index 000000000..44625e929 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/blocklists.md new file mode 100644 index 000000000..8b03cc056 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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. +2. Go to the _Servers_ section. +3. Select the required server. +4. 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). +2. Click _New issue_. +3. Click _Blocklist request_ and fill out the form. +4. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/parental-control.md new file mode 100644 index 000000000..f65661960 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/security-features.md new file mode 100644 index 000000000..f3185c7ba --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/setting-up-filtering/user-rules.md new file mode 100644 index 000000000..11b3d99da --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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_. + +2. Go to the _Servers_ section. + +3. Select the required server. + +4. Click the _User rules_ option. + +5. 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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/companies.md new file mode 100644 index 000000000..b21375a03 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/query-log.md new file mode 100644 index 000000000..e20fc8f7c --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics-and-log.md new file mode 100644 index 000000000..c55c81f8a --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/statistics.md new file mode 100644 index 000000000..4a6688ec8 --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/statistics-and-log/traffic-destination.md new file mode 100644 index 000000000..83ff7528e --- /dev/null +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/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)