You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README_en.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,29 +18,27 @@ Follow our channel for the latest news, or join our group for discussion!
18
18
# Features
19
19
- The DNS server uses Tencent and Alibaba's public DNS, you can also change it in the DNS settings of AdGuardHome to meet your needs.
20
20
- Only built-in [Autumn Breeze Ad Rule](https://github.com/TG-Twilight/AWAvenue-Ads-Rule), accurate, lightweight, and low false positives.
21
-
- In Magisk/KernelSU, you can start/stop the module in real-time through the module switch.
21
+
- In Magisk/KernelSU, you can start/stop the module in real-time using the module switch, or you can simulate the module switch in the shell.
22
+
```shell
23
+
touch /data/adb/modules/AdguardHome/disable
24
+
```
22
25
- You can modify the configuration file located in `/data/adb/agh/scripts/config.sh` to adjust the configuration.
23
-
- When overwriting installation, the original module will be automatically backed up.
26
+
- When updating the module, users can choose whether to keep the original configuration file, even if you choose not to keep it, the original configuration file will be automatically backed up to the `/data/adb/agh/backup` directory.
24
27
25
28
# FAQ
26
-
> Q: Why can't the module block some ads?
29
+
> Q: Why can't the module block all ads?
27
30
28
-
> A: The module blocks ads by forwarding DNS requests on port 53, so it cannot block ads transmitted over HTTPS or ads on the same domain as normal content, such as Zhihu, Youtube, etc.
31
+
> A: The module blocks ads by forwarding DNS requests on port 53, so it cannot block ads transmitted over HTTPS or ads on the same domain as normal content, such as Zhihu, Youtube, etc., but fortunately, most ads still prefer to use DNS requests on port 53.
29
32
30
-
> Q: Why does the page slow down after installing the module?
31
-
32
-
> A: Because the module forwards all DNS requests to AdGuardHome, which then forwards them to the upstream public DNS, adding an extra layer of forwarding, but the module has optimistic caching enabled by default, which greatly reduces latency on the second visit.
33
-
34
-
> Q: Why can't I access a page that I could access before after a while?
33
+
> Q: Can the module be used with other proxy modules/software?
35
34
36
-
> A: Because public DNS requests are slow, the module's default configuration file has optimistic caching enabled, which may cause some outdated IPs to continue to be used after they expire, you can clear the DNS cache in the background to alleviate this, or disable optimistic caching.
35
+
> A: Yes, general proxy apps can be directly compatible (here we recommend using [FlClash](https://github.com/chen08209/FlClash)), and AdGuardHome's DNS queries will pass through the VPN, other proxy modules can be used as needed, and the automatic iptables rules can be turned off for normal DNS use.
37
36
38
-
> Q: Can the module be used with other proxy modules/software?
37
+
> Q: Why not integrate with KernelSU's WebUI?
39
38
40
-
> A: Yes, general proxy apps are directly compatible, and AdGuardHome's DNS queries will pass through the VPN, other proxy modules can be used as needed, you can disable automatic iptables rules to use it as a regular DNS.
39
+
> A: Because KernelSU's WebUI cannot display confirmation pop-ups, some functions of AdGuardHome's management end cannot be used, so it is not integrated for the time being.
0 commit comments