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
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
The clients on our network are running on Dual Stack and can access the internet using both IPv4 and IPv6. The browser (Chrome, Firefox) mixes both IP sources when loading a website. This works well for some websites, while others encounter (big) issues.
Proposed solution
When the 'Disable resolving of IPv6 addresses' function in AdGuard Home is enabled, all problems disappear, but the clients no longer use IPv6. To enable smooth operation in mixed environments, it would be sensible to block only specific domains from receiving an IPv6 resolving. For this, there should be an option to list domains that should not receive IPv6 resolutions.
Alternatives considered and additional information
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
The clients on our network are running on Dual Stack and can access the internet using both IPv4 and IPv6. The browser (Chrome, Firefox) mixes both IP sources when loading a website. This works well for some websites, while others encounter (big) issues.
Proposed solution
When the 'Disable resolving of IPv6 addresses' function in AdGuard Home is enabled, all problems disappear, but the clients no longer use IPv6. To enable smooth operation in mixed environments, it would be sensible to block only specific domains from receiving an IPv6 resolving.
For this, there should be an option to list domains that should not receive IPv6 resolutions.
Alternatives considered and additional information
No response
The text was updated successfully, but these errors were encountered: