默认情况下dns不通怎么回事 #2499

HuengchI · 2023-04-15T05:43:58Z

HuengchI
Apr 15, 2023

问题复现步骤：

在Release页面下载最新安装包
手动配置一个节点，点击“可用性测试”，出现“延迟数字”（表明节点连接成功）
打开总开关，设置tcp节点为刚刚配置的节点
然后路由器上面访问任何网址dns都无法解析。面板上点"百度，谷歌， github"测试也全部错误
在/etc/resolvd.conf中手动加入一个nameserver后dns恢复。但是还是翻不了。

xiaorouji · 2023-04-15T14:06:31Z

xiaorouji
Apr 15, 2023
Maintainer

请上传完整的日志

0 replies

HuengchI · 2023-04-15T15:13:27Z

HuengchI
Apr 15, 2023
Author

@xiaorouji
感谢🙏

开机之后`passwall`的日志

2023-04-14 14:01:43: 删除相关防火墙规则完成。
2023-04-14 14:01:43: 清空并关闭相关程序和缓存完成。
2023-04-14 14:01:43: TCP节点：[香港云]，监听端口：1041
2023-04-14 14:01:43: UDP节点没有选择或为空，不代理UDP。
2023-04-14 14:01:43: 过滤服务配置：准备接管域名解析...
2023-04-14 14:01:43:   - 域名解析：dns2tcp + 使用(TCP节点)解析域名...
2023-04-14 14:01:43:   * 请确认上游 DNS 支持 TCP 查询，如非直连地址，确保 TCP 代理打开，并且已经正确转发！
2023-04-14 14:01:43:   - 以上所列以外及默认：127.0.0.1#15353
2023-04-14 14:01:43:   - PassWall必须依赖于Dnsmasq，如果你自行配置了错误的DNS流程，将会导致域名(直连/代理域名)分流失效！！！
2023-04-14 14:01:43: 开始加载防火墙规则...
2023-04-14 14:01:43: 加入负载均衡的节点到ipset[vpsiplist]直连完成
2023-04-14 14:01:43: 加入所有节点到ipset[vpsiplist]直连完成
2023-04-14 14:01:43: 加载路由器自身 TCP 代理...
2023-04-14 14:01:43:   - [2]将上游 DNS 服务器 1.1.1.1:53 加入到路由器自身代理的 TCP 转发链
2023-04-14 14:01:43:   - [0]，屏蔽代理UDP 端口：80,443
2023-04-14 14:01:43: TCP默认代理：使用TCP节点[香港云] [全局代理](REDIRECT:1041)代理所有端口
2023-04-14 14:01:43: 防火墙规则加载完成！
2023-04-14 14:01:43: 重启 dnsmasq 服务
2023-04-14 14:01:43: 运行完成！

`cat /etc/resolv.conf`

search lan
nameserver 127.0.0.1
nameserver ::1

`nslookup www.baidu.com`

nslookup: write to '127.0.0.1': Connection refused
nslookup: write to '::1': Connection refused
;; connection timed out; no servers could be reached

`System Log`

Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: started, version 2.86 cachesize 150
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using nameserver 223.5.5.5#53
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Sat Apr 15 23:01:43 2023 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Sat Apr 15 23:01:43 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:01:43 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:01:43 2023 cron.err crond[22154]: crond (busybox 1.35.0) started, log level 5
Sat Apr 15 23:01:48 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:01:48 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:01:53 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:01:53 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:01:58 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:01:58 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:02:03 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:02:03 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:02:08 2023 daemon.crit dnsmasq[1]: recompile with HAVE_IPSET defined to enable ipset directives at line 1 of /tmp/dnsmasq.d/passwall/ipset.conf
Sat Apr 15 23:02:08 2023 daemon.crit dnsmasq[1]: FAILED to start up
Sat Apr 15 23:02:08 2023 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 6 crashes, 0 seconds since last crash

`dnsmasq; nslookup www.baidu.com`

Server:         127.0.0.1
Address:        127.0.0.1:53

** server can't find www.baidu.com: REFUSED

** server can't find www.baidu.com: REFUSED

3 replies

TAEKING2008 Apr 18, 2023

大大，我更新了「规则管理」里的手动更新后，不管什么网站都是DNS解析错误。把软路由关了，重新网络自动设置，就能打开。

xiaorouji Apr 18, 2023
Maintainer

@HuengchI
recompile with HAVE_IPSET defined to enable ipset directives.
你的dnsmasq-full沒有開啟ipset支援

HuengchI Apr 20, 2023
Author

@xiaorouji 不知道哪里配置错了？

HuengchI · 2023-04-19T01:06:08Z

HuengchI
Apr 19, 2023
Author

@xiaorouji

你的dnsmasq-full沒有開啟ipset支援

感谢。我重新安装了 dnsmasq-full这个package，dns 的问题似乎解决了。

但是谷歌连接还是失败，不知道哪里配置错误了？

passwall日志

2023-04-19 08:57:38: 删除相关防火墙规则完成。
2023-04-19 08:57:38: 清空并关闭相关程序和缓存完成。
2023-04-19 08:57:38: TCP节点：[阿美莉卡]，监听端口：1041
2023-04-19 08:57:38: 过滤服务配置：准备接管域名解析...
2023-04-19 08:57:38:   - 域名解析：使用UDP协议请求DNS（8.8.8.8）...
2023-04-19 08:57:38:   * 要求代理 DNS 请求，如上游 DNS 非直连地址，确保 UDP 代理打开，并且已经正确转发！
2023-04-19 08:57:38:   - 以上所列以外及默认：8.8.8.8
2023-04-19 08:57:38:   - PassWall必须依赖于Dnsmasq，如果你自行配置了错误的DNS流程，将会导致域名(直连/代理域名)分流失效！！！
2023-04-19 08:57:38: 开始加载防火墙规则...
2023-04-19 08:57:38: 加入负载均衡的节点到ipset[vpsiplist]直连完成
2023-04-19 08:57:38: 加入所有节点到ipset[vpsiplist]直连完成
2023-04-19 08:57:38: 加载路由器自身 TCP 代理...
2023-04-19 08:57:38:   - [0]，屏蔽代理UDP 端口：80,443
2023-04-19 08:57:38: 加载路由器自身 UDP 代理...
2023-04-19 08:57:38:   - [2]将上游 DNS 服务器 8.8.8.8:53 加入到路由器自身代理的 UDP 转发链
2023-04-19 08:57:38: TCP默认代理：使用TCP节点[阿美莉卡] [全局代理](REDIRECT:1041)代理所有端口
2023-04-19 08:57:38: UDP默认代理：使用UDP节点[阿美莉卡] [防火墙列表](TPROXY:1041)代理所有端口
2023-04-19 08:57:38: 防火墙规则加载完成！
2023-04-19 08:57:38: 重启 dnsmasq 服务
2023-04-19 08:57:38: 运行完成！

SystemLog中似乎存在一些错误日志

Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--restore-mark"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): Couldn't load match `conntrack':No such file or directory
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall:
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--save-mark"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): Couldn't load match `socket':No such file or directory
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall:
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--tproxy-mark"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--tproxy-mark"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--to-ports"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: iptables v1.8.7 (nf_tables): unknown option "--tproxy-mark"
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: Try `iptables -h' or 'iptables --help' for more information.
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: # Warning: iptables-legacy tables present, use iptables-legacy-save to see them
Wed Apr 19 08:55:35 2023 daemon.notice procd: /etc/rc.d/S99zzz_passwall: # Warning: iptables-legacy tables present, use iptables-legacy-save to see them

2 replies

xiaorouji Apr 20, 2023
Maintainer

可能缺少
iptables-mod-conntrack-extra
iptables-mod-socket

HuengchI Apr 20, 2023
Author

感谢回复。我装上了这两个包，还是访问不了谷歌。

curl -I https://www.google.com

curl: (7) Failed to connect to www.google.com port 443 after 2 ms: Error

我应该如何排查错误呢？

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

默认情况下dns不通怎么回事 #2499

{{title}}

Replies: 3 comments 5 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

默认情况下dns不通怎么回事 #2499

HuengchI Apr 15, 2023

问题复现步骤：

Replies: 3 comments · 5 replies

xiaorouji Apr 15, 2023 Maintainer

HuengchI Apr 15, 2023 Author

相关配置截图

开机之后passwall的日志

cat /etc/resolv.conf

nslookup www.baidu.com

System Log

dnsmasq; nslookup www.baidu.com

TAEKING2008 Apr 18, 2023

xiaorouji Apr 18, 2023 Maintainer

HuengchI Apr 20, 2023 Author

HuengchI Apr 19, 2023 Author

xiaorouji Apr 20, 2023 Maintainer

HuengchI Apr 20, 2023 Author

HuengchI
Apr 15, 2023

Replies: 3 comments 5 replies

xiaorouji
Apr 15, 2023
Maintainer

HuengchI
Apr 15, 2023
Author

开机之后`passwall`的日志

`cat /etc/resolv.conf`

`nslookup www.baidu.com`

`System Log`

`dnsmasq; nslookup www.baidu.com`

xiaorouji Apr 18, 2023
Maintainer

HuengchI Apr 20, 2023
Author

HuengchI
Apr 19, 2023
Author

xiaorouji Apr 20, 2023
Maintainer

HuengchI Apr 20, 2023
Author