-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #147 from AdguardTeam/known-issues
Add an article about known AdGuard DNS issues
- Loading branch information
Showing
1 changed file
with
59 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
title: Known issues | ||
sidebar_position: 2 | ||
--- | ||
|
||
After setting up AdGuard DNS, some users may find that it doesn’t work properly: they see a message that their device is not connected to AdGuard DNS and the requests from that device are not displayed in the Query log. This can happen because of certain hidden settings in your browser or operating system. Let’s look at several common issues and their solutions. | ||
|
||
:::tip | ||
|
||
You can check the status of AdGuard DNS on the [test page](https://adguard.com/test.html). | ||
|
||
::: | ||
|
||
## Chrome’s secure DNS settings | ||
|
||
If you’re using Chrome and you don’t see any requests in your AdGuard DNS dashboard, this may be because Chrome uses its own DNS server. Here’s how you can disable it: | ||
|
||
1. Open Chrome’s settings. | ||
1. Navigate to *Privacy and security*. | ||
1. Select *Security*. | ||
1. Scroll down to *Use secure DNS*. | ||
1. Disable the feature. | ||
|
||
![Chrome’s Use secure DNS feature](https://cdn.adtidy.org/content/kb/dns/private/solving_problems/known_issues/secure-dns.png) | ||
|
||
If you disable Chrome’s own DNS settings, the browser will use the DNS specified in your operating system, which should be AdGuard DNS if you've set it up correctly. | ||
|
||
## iCloud Private Relay (Safari, macOS, and iOS) | ||
|
||
If you enable iCloud Private Relay in your device settings, Safari will use Apple’s DNS addresses, which will override the AdGuard DNS settings. | ||
|
||
Here’s how you can disable iCloud Private Relay on your iPhone: | ||
|
||
1. Open *Settings* and tap your name. | ||
1. Select *iCloud* → *Private Relay*. | ||
1. Turn off Private Relay. | ||
|
||
![iOS Private Relay](https://cdn.adtidy.org/content/kb/dns/private/solving_problems/known_issues/private-relay.png) | ||
|
||
On your Mac: | ||
|
||
1. Open *System Settings* and click your name or *Apple ID*. | ||
1. Select *iCloud* → *Private Relay*. | ||
1. Turn off Private Relay. | ||
1. Click *Done*. | ||
|
||
![macOS Private Relay](https://cdn.adtidy.org/content/kb/dns/private/solving_problems/known_issues/mac-private-relay.png) | ||
|
||
## Advanced Tracking and Fingerprinting Protection (Safari, starting from iOS 17) | ||
|
||
After the iOS 17 update, Advanced Tracking and Fingerprinting Protection may be enabled in Safari settings, which could potentially have a similar effect to iCloud Private Relay bypassing AdGuard DNS settings. | ||
|
||
Here’s how you can disable Advanced Tracking and Fingerprinting Protection: | ||
|
||
1. Open *Settings* and scroll down to *Safari*. | ||
1. Tap *Advanced*. | ||
1. Disable *Advanced Tracking and Fingerprinting Protection*. | ||
|
||
![iOS Tracking and Fingerprinting Protection *mobile](https://cdn.adtidy.org/content/kb/dns/private/solving_problems/known_issues/ios-tracking-and-fingerprinting.png) |