We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstream.proxy
dst.addr as a domain should be read from socks5 packet
dst.add is now an IP address even if I do a domain fetch
The text was updated successfully, but these errors were encountered:
Since DNS name is already resolved by browser before it intercepted by AdGuard, it is complicated and requires workaround (fake DNS server).
However, I created feature request in our filtering engine, you may track this issue there:
AdguardTeam/CoreLibs#1386
Sorry, something went wrong.
But I can find domains in the logs printer. Why's that?
AdGuard detects domain name in first packets of connection but this happens after connection is already established
Thank you for your patience and responses.
No branches or pull requests
Steps to reproduce
upstream.proxy
to a socks5 serverExpected behavior
dst.addr as a domain should be read from socks5 packet
Actual behavior
dst.add is now an IP address even if I do a domain fetch
Screenshot:
Customer ID
Your environment
The text was updated successfully, but these errors were encountered: