Update info on DNS filtering in automatic proxy mode.md #715
Conversation
This file contains hidden or 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
обновить раздел Базы знаний про AdGuard для Android: добавить информацию о DNS-фильтрации в режиме «Автоматический прокси»
![windsurf-bot[bot]](https://avatars.githubusercontent.com/in/1066231?s=60&v=4){kind=small}
|
|
||
| :::note | ||
|
|
||
| Please note that DNS filtering will still be active in *Automatic proxy* mode, and your device might not be able to entirely filter out DNS requests from apps. If we compare the situation to VPN mode, apps there are excluded from the local VPN by system means, therefore the system resolver "sees" which apps are included in the VPN and which are not, and either allows them into the local VPN or lets them bypass it. On the other hand, DNS requests come from the system resolver, not from the application. In *Automatic proxy* routing mode, it is only possible to exclude traffic from applications, not their DNS queries — because they are seen by AdGuard as queries from the system. |
There was a problem hiding this comment.
There appears to be a potential wording issue in the note. The phrase 'might not be able to entirely filter out DNS requests from apps' seems to contradict the later explanation that DNS filtering is still active. Consider rewording to 'might not be able to selectively filter out DNS requests from specific apps' to better reflect that DNS filtering works but can't be selectively applied to specific apps in this mode.
|
Preview was deployed to: https://pull-request-715.kb-adg.pages.dev/ |
|
Preview was deployed to: https://pull-request-715.kb-adg.pages.dev/ |
an-martynova
changed the title
an-martynova
changed the title
|
Preview was deployed to: https://pull-request-715.kb-adg.pages.dev/ |
| @@ -132,6 +132,12 @@ The *Local VPN* mode doesn't allow AdGuard to be used simultaneously with other | |||
|
|
|||
| - *Automatic proxy* is an alternative traffic routing method that does not require the use of a VPN. One significant advantage is that it can be run in parallel with a VPN. This mode requires root access. | |||
|
|
|||
| :::note | |||
|
|
|||
| Please note that DNS filtering will still be active in *Automatic proxy* mode, and your device might not be able to selectively filter out DNS requests from specific apps. If we compare the situation to VPN mode, apps there are excluded from the local VPN by system means, therefore the system resolver "sees" which apps are included in the VPN and which are not, and either allows them into the local VPN or lets them bypass it. On the other hand, DNS requests come from the system resolver, not from the application. In *Automatic proxy* routing mode, it is only possible to exclude traffic from applications, not their DNS queries — because they are seen by AdGuard as queries from the system. | |||
There was a problem hiding this comment.
Suggested change
| Please note that DNS filtering will still be active in *Automatic proxy* mode, and your device might not be able to selectively filter out DNS requests from specific apps. If we compare the situation to VPN mode, apps there are excluded from the local VPN by system means, therefore the system resolver "sees" which apps are included in the VPN and which are not, and either allows them into the local VPN or lets them bypass it. On the other hand, DNS requests come from the system resolver, not from the application. In *Automatic proxy* routing mode, it is only possible to exclude traffic from applications, not their DNS queries — because they are seen by AdGuard as queries from the system. | |
| Please note that DNS filtering will still be active in *Automatic proxy* routing mode, and your device may not be able to filter DNS requests from specific apps. In *VPN* routing mode, apps are excluded from the local VPN by system means. Therefore, the system resolver sees which apps are included in the VPN and which are not. It either allows them into the local VPN or lets them bypass it. However, DNS requests come from the system resolver, not the application. In *Automatic proxy* mode, it is only possible to exclude traffic from applications, not their DNS queries, because AdGuard sees them as system queries. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
обновить раздел Базы знаний про AdGuard для Android: добавить информацию о DNS-фильтрации в режиме «Автоматический прокси»