In the AdGuard for iOS app, the DNS filtering section is missing when the DNS implementation is set to Native (found in AdGuard app > Protection > DNS Protection). The DNS filtering section only appears when the DNS implementation is set to AdGuard DNS.
I do not recall this behavior in iOS 17, where the DNS filtering section seemed to be available regardless of the DNS implementation setting. This change limits the functionality available when using the Native DNS implementation, which is unexpected.
Steps to Reproduce:
Open AdGuard for iOS.
Navigate to Protection > DNS Protection.
Set DNS Implementation to Native.
Observe that the DNS filtering section is missing.
Change DNS Implementation to AdGuard.
Observe that the DNS filtering section is now visible.
Expected Behavior
The DNS filtering section should be accessible regardless of whether Native or AdGuard DNS is selected as the DNS implementation, or at least this behaviour should be clarified in the app documentation.
Actual Behavior
The DNS filtering section is only accessible when AdGuard DNS is selected.
Please answer the following questions for yourself before submitting an issue
AdGuard version
4.5.7
Environment
Ad Blocking
AdGuard Base filter, AdGuard Mobile Ads filter
Privacy
AdGuard Tracking Protection filter
Social
AdGuard Social Media filter
Annoyances
AdGuard Annoyances filter
Security
No response
Other
No response
Language-specific
No response
Advanced protection for Safari
Which DNS server do you use?
Quad9
DNS protocol
DNS-over-HTTPS
Custom DNS
No response
DNS filtering
Custom DNS filter
AdGuard DNS
DNS implementation
Native
Tunnel mode
Split-Tunnel
Low-level settings
Bootstrap server: Fallback server: Blocking mode, etc:
Issue Details
In the AdGuard for iOS app, the DNS filtering section is missing when the DNS implementation is set to Native (found in AdGuard app > Protection > DNS Protection). The DNS filtering section only appears when the DNS implementation is set to AdGuard DNS.
I do not recall this behavior in iOS 17, where the DNS filtering section seemed to be available regardless of the DNS implementation setting. This change limits the functionality available when using the Native DNS implementation, which is unexpected.
Steps to Reproduce:
Expected Behavior
The DNS filtering section should be accessible regardless of whether Native or AdGuard DNS is selected as the DNS implementation, or at least this behaviour should be clarified in the app documentation.
Actual Behavior
The DNS filtering section is only accessible when AdGuard DNS is selected.
Screenshots
Screenshot 1
Additional Information
No response