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
你好
读rules.yaml后发现有IP-CIDR和IP-CIDR6的分流。如果简单的把这个ruleset分流到某节点,并且这个ruleset在国外站点domain类分流规则上面(优先级高)的情况下会导致访问国外站全部过一遍dns解析,哪怕国外domain类分流有匹配规则。此时会导致dns泄漏。
domain和ip规则混合的情况下只能用classical类型behavior,然而clash对于非ipcidr类型的ruleset无法整个ruleset添加no-resolve。
麻烦在每条IP-CIDR规则后面添加 no-resolve 选项,(帮助小白)避免dns泄漏发生。
谢谢。
The text was updated successfully, but these errors were encountered:
问题已收到,目前的生成脚本有些混乱,在整理后会添加此功能。
Sorry, something went wrong.
#45
No branches or pull requests
你好
读rules.yaml后发现有IP-CIDR和IP-CIDR6的分流。如果简单的把这个ruleset分流到某节点,并且这个ruleset在国外站点domain类分流规则上面(优先级高)的情况下会导致访问国外站全部过一遍dns解析,哪怕国外domain类分流有匹配规则。此时会导致dns泄漏。
domain和ip规则混合的情况下只能用classical类型behavior,然而clash对于非ipcidr类型的ruleset无法整个ruleset添加no-resolve。
麻烦在每条IP-CIDR规则后面添加 no-resolve 选项,(帮助小白)避免dns泄漏发生。
谢谢。
The text was updated successfully, but these errors were encountered: