8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
查询 AAAA
; <<>> DiG 9.16.1-Ubuntu <<>> @192.168.0.103 -p5302 www.google.com AAAA ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19996 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 8 ;; QUESTION SECTION: ;www.google.com. IN AAAA ;; ANSWER SECTION: www.google.com. 600 IN AAAA 2001::4a56:8e37
查询 A
; <<>> DiG 9.16.1-Ubuntu <<>> @192.168.0.103 -p5302 www.google.com A ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51649 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 299 IN A 172.217.160.100
ts-dns 日志显示,因为 AAAA 类型查询不返回 ipv4,所以被当做 clean 处理,即使域名符合 gfwlist 也不会再次进行查询
INFO[0001] [0x4e1c] [server.go:238] cn/empty ipv4, group: clean QUESTION=www.google.com. Q_TYPE=AAAA SRC="192.168.0.95:53871" INFO[0003] [0xc9c1] [server.go:244] match gfwlist, group: dirty QUESTION=www.google.com. Q_TYPE=A SRC="192.168.0.95:60054"
The text was updated successfully, but these errors were encountered:
目前暂时通过在dirty组中用rules规定google.com强制走该组解析解决,但是我觉得这个判断逻辑是不是应该针对 AAAA 记录查询修改一下
Sorry, something went wrong.
即将发布的v1.0版本(#41)将修复这个问题。clean和dirty组将不再做特殊处理,匹配规则将由rules/gfwlist明确指定,并通过redirector进行更灵活的重定向(#25)。 新版本重构了大量代码,配置文件相比v0略有改动,欢迎review。
rules
gfwlist
redirector
v1.0已发布
No branches or pull requests
查询 AAAA
查询 A
ts-dns 日志显示,因为 AAAA 类型查询不返回 ipv4,所以被当做 clean 处理,即使域名符合 gfwlist 也不会再次进行查询
The text was updated successfully, but these errors were encountered: