Known issues

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.

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.
2. Navigate to Privacy and security.
3. Select Security.
4. Scroll down to Use secure DNS.
5. Disable the feature.

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.
2. Select iCloud → Private Relay.
3. Turn off Private Relay.

On your Mac:

1. Open System Settings and click your name or Apple ID.
2. Select iCloud → Private Relay.
3. Turn off Private Relay.
4. Click Done.

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.
2. Tap Advanced.
3. Disable Advanced Tracking and Fingerprinting Protection.