### Prerequisites

Before we dive into the issue at hand, let's make sure we have all the necessary information to provide a helpful solution. Here are the prerequisites for this issue:

Platform (OS and CPU architecture)

• Linux: We are using a Linux-based system for this issue.
• AMD64 (aka x86_64): The CPU architecture is AMD64, also known as x86_64.

Installation

• Docker: We are using Docker for the installation of AdGuard Home.

Setup

• On a router, DHCP is handled by AdGuard Home: AdGuard Home is handling the DHCP on the router.

AdGuard Home version

• 0.107.61: We are using version 0.107.61 of AdGuard Home.

Action

To reproduce the issue, follow these steps:

1. On the client machine at 10.10.10.2 run dig example.com and observe output.
2. In AdGuard add a DNS rewrite for example.com to 10.10.10.99.
3. On the client machine at 10.10.10.2 run dig example.com and observe output.
4. Globally disable protection in ADGuard.
5. On the client machine at 10.10.10.2 run dig example.com and observe output.
6. Globally enable protection in AdGuard.
7. In AdGuard add a Persistent client for a local machine at 10.10.10.2, unchecking "Use global settings".
8. On the client machine at 10.10.10.2 run dig example.com and observe output.

Expected result

Based on the issue description, the expected results are as follows:

1. dig returns 96.7.128.198.
2. dig returns 10.10.10.99.
3. dig returns 96.7.128.198.
4. dig returns 96.7.128.198.
5. dig returns 10.10.10.99.

Actual result

However, the actual results are as follows:

1. dig returns 96.7.128.198.
2. dig returns 10.10.10.99.
3. dig returns 96.7.128.198.
4. dig returns 96.7.128.198.
5. dig returns 96.7.128.198.

Additional information and/or screenshots

Unfortunately, there are no additional information or screenshots provided to help with the issue.

The issue at hand is related to the behavior of AdGuard Home when disabling protection on a client machine. The expected result is that the DNS rewrite should still be active, but the actual result is that the DNS rewrite is not active when protection is disabled on the client machine.

There are several possible causes for this issue:

• Misconfigured AdGuard Home: AdGuard Home may be misconfigured, leading to the incorrect behavior.
• Client machine configuration: The client machine may be configured incorrectly, leading to the issue.
• AdGuard Home version: The version of AdGuard Home being used may be causing the issueTroubleshooting Steps =========================

To troubleshoot this issue, we can follow these steps:

1. Verify AdGuard Home configuration: Verify that AdGuard Home is configured correctly.
2. Check client machine configuration: Check the client machine configuration to ensure it is correct.
3. Update AdGuard Home version: Update AdGuard Home to the latest version to see if the issue is resolved.
4. Disable and re-enable protection: Disable and re-enable protection on the client machine to see if the issue is resolved.

Q: What is the issue with AdGuard Home?

A: The issue with AdGuard Home is that when protection is disabled on a client machine, the DNS rewrite is not active. This is contrary to the expected behavior, where the DNS rewrite should still be active even when protection is disabled.

Q: What are the expected results?

A: The expected results are as follows:

1. dig returns 96.7.128.198.
2. dig returns 10.10.10.99.
3. dig returns 96.7.128.198.
4. dig returns 96.7.128.198.
5. dig returns 10.10.10.99.

Q: What are the actual results?

A: The actual results are as follows:

1. dig returns 96.7.128.198.
2. dig returns 10.10.10.99.
3. dig returns 96.7.128.198.
4. dig returns 96.7.128.198.
5. dig returns 96.7.128.198.

Q: What are the possible causes of this issue?

A: There are several possible causes for this issue:

• Misconfigured AdGuard Home: AdGuard Home may be misconfigured, leading to the incorrect behavior.
• Client machine configuration: The client machine may be configured incorrectly, leading to the issue.
• AdGuard Home version: The version of AdGuard Home being used may be causing the issue.

Q: How can I troubleshoot this issue?

A: To troubleshoot this issue, you can follow these steps:

1. Verify AdGuard Home configuration: Verify that AdGuard Home is configured correctly.
2. Check client machine configuration: Check the client machine configuration to ensure it is correct.
3. Update AdGuard Home version: Update AdGuard Home to the latest version to see if the issue is resolved.
4. Disable and re-enable protection: Disable and re-enable protection on the client machine to see if the issue is resolved.

Q: What is the expected behavior of AdGuard Home when protection is disabled?

A: The expected behavior of AdGuard Home when protection is disabled is that the DNS rewrite should still be active. This is defined in issue #1558, which states that "Disable Protection" should keep DNS rewrites still active.

Q: Why is the DNS rewrite not active when protection is disabled?

A: The DNS rewrite is not active when protection is disabled because of a bug in AdGuard Home. This bug is causing the DNS rewrite to be disabled when protection is disabled on a client machine.

Q: How can I resolve this issue?

A: To resolve this issue, you can try the following:

1. Update AdGuard Home version: Update AdGuard Home to the latest version to see if the issue is resolved.
2. Disable and re-enable protection: Disable and re-enable protection on the client machine to see if the issue is resolved.
3. Verify AdGuard Home configuration: Verify that Ad Home is configured correctly.
4. Check client machine configuration: Check the client machine configuration to ensure it is correct.

In conclusion, the issue with AdGuard Home is that when protection is disabled on a client machine, the DNS rewrite is not active. This is contrary to the expected behavior, where the DNS rewrite should still be active even when protection is disabled. We have identified several possible causes for this issue and provided troubleshooting steps to resolve the issue.