搭配PaoPaoGateway访问USE_MARK_DATA中的域名时偶尔不会返回FAKEIP #74

Dontcampy · 2023-11-26T13:47:45Z

Dontcampy
Nov 26, 2023

当发生此情况的时候, 使用另一台设备尝试解析这个域名有可能也会获得一个非FAKEIP

过一段时间会恢复

写到一半发现Github的ip也出问题了，但没一会又变回来了

主路由的dns只配置了一个PaoPaoDNS

PaoPaoDNS部署配置

services:
  paopaodns:
    image: sliamb/paopaodns:latest
    container_name: PaoPaoDNS
    restart: always
    volumes:
      - /share/Container/paopaodns:/data
    environment:
      - TZ=Asia/Shanghai
      - UPDATE=weekly
      - DNS_SERVERNAME=PaoPaoDNS,blog.03k.org
      - DNSPORT=53
      - SOCKS5=no
      - CNAUTO=yes
      - IPV6=no
      - CNFALL=yes
      - CUSTOM_FORWARD=192.168.50.195:53
      - AUTO_FORWARD=yes
      - CN_TRACKER=yes
      - SAFEMODE=no
      - RULES_TTL=60
      - ADDINFO=yes
      - HTTP_FILE=yes
      - SERVER_IP=192.168.50.194
      - USE_MARK_DATA=yes
    ports:
      - "53:53/udp"
      - "53:53/tcp"
      - "5304:5304/udp"
      - "5304:5304/tcp"
      - "7889:7889/tcp"

PaoPaoGateway配置

#paopao-gateway

# mode=socks5|ovpn|yaml|suburl|free
# default: free
mode=socks5

# Set fakeip's CIDR here
# default: fake_cidr=7.0.0.0/8
fake_cidr=7.0.0.0/8

# Set your trusted DNS here
# default: dns_ip=1.0.0.1
dns_ip=192.168.50.194
# default: dns_port=53
# If used with PaoPaoDNS, you can set the 5304 port
dns_port=5304

# Clash's web dashboard
clash_web_port="80"
clash_web_password="clashpass"

# default：openport=no
# socks+http mixed 1080
openport=no

# default: udp_enable=no
udp_enable=no

# default:30
sleeptime=30

# socks5 mode settting
# default: socks5_ip=gatewayIP
socks5_ip="192.168.50.128"
# default: socks5_port="7890"
socks5_port="20170"

# ovpn mode settting
# The ovpn file in the same directory as the ppgw.ini.
# default: ovpnfile=custom.ovpn
ovpnfile="custom.ovpn"
ovpn_username=""
ovpn_password=""

# yaml mode settting
# The yaml file in the same directory as the ppgw.ini.
# default: yamlfile=custom.yaml
yamlfile="custom.yaml"

# suburl mode settting
suburl="https://..."
subtime=1d

# fast_node=check/yes/no
fast_node=yes
test_node_url="https://www.youtube.com/generate_204"
ext_node="Traffic|Expire| GB|Days|Date"
cpudelay="3000"

# dns burn setting
# depand on fast_node=yes & mode=suburl/yaml
dns_burn=no
# If used with PaoPaoDNS, you can set the PaoPaoDNS:53
ex_dns="PaoPaoDNS:53"

# Network traffic records
net_rec=yes
max_rec=5000

PaoPaoDNS debug.sh

[INFO] images build time : 2023-11-23 16:48:29 UTC
[OK]DATA_writeable
[OK]DATA_readable
[INFO] NETWORK
*********************************************************************************

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    inet 127.0.0.1/8 scope host lo
19: eth0@if20: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP 
    inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
default via 172.18.0.1 dev eth0 
172.18.0.0/16 dev eth0 scope link  src 172.18.0.2 
PING 223.5.5.5 (223.5.5.5): 56 data bytes
64 bytes from 223.5.5.5: seq=0 ttl=118 time=5.150 ms

--- 223.5.5.5 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 5.150/5.150/5.150 ms
PING 119.29.29.29 (119.29.29.29): 56 data bytes
64 bytes from 119.29.29.29: seq=0 ttl=54 time=5.411 ms

--- 119.29.29.29 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 5.411/5.411/5.411 ms
Server:         223.5.5.5
Address:        223.5.5.5#53

Non-authoritative answer:
www.taobao.com  canonical name = www.taobao.com.danuoyi.tbcache.com.
Name:   www.taobao.com.danuoyi.tbcache.com
Address: 112.132.36.204
Name:   www.taobao.com.danuoyi.tbcache.com
Address: 112.132.36.205
Name:   www.taobao.com.danuoyi.tbcache.com
Address: 2408:8744:600:2:3::3e7
Name:   www.taobao.com.danuoyi.tbcache.com
Address: 2408:8744:600:2:3::3e6

Server:         119.29.29.29
Address:        119.29.29.29#53

Non-authoritative answer:
www.qq.com      canonical name = ins-r23tsuuf.ias.tencent-cloud.net.
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 58.246.163.58
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 116.128.170.212
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 2408:80f1:21:c120::e
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 2408:80f1:21:c120::c

*********************************************************************************

[INFO] ENV
*********************************************************************************

====ENV TEST====
[OK]DATA_writeable-
[OK]DATA_readable-
MEM:500m 1000m 500000 1500mb
prefPC:100
CORES:-4-
POWCORES:-4-
ulimit :-1048576-
FDLIM :-4096-
TZ:-Asia/Shanghai-
UPDATE:-weekly-
DNS_SERVERNAME:-PaoPaoDNS,blog.03k.org-
SERVER_IP:-192.168.50.194-
ETHIP:-172.18.0.2-
DNSPORT:-53-
SOCKS5:-no-
CNAUTO:-yes-
IPV6:-no-
CNFALL:-yes-
CUSTOM_FORWARD:-192.168.50.195:53-
AUTO_FORWARD:-yes-
AUTO_FORWARD_CHECK:-yes-
USE_MARK_DATA:-yes-
RULES_TTL:-60-
CUSTOM_FORWARD_TTL:-0-
SHUFFLE:-no-
CN_TRACKER:-yes-
USE_HOSTS:-no-
HTTP_FILE:-yes-
SAFEMODE:-no-
QUERY_TIME:-2000ms-
ADDINFO:-yes-
PLATFORM:-Linux 033332638d8b 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 Linux-
====ENV TEST====
mosdns kkkgo/mosdns:231115.1
*********************************************************************************

[INFO] PS
*********************************************************************************

PID   USER     TIME  COMMAND
    1 root      0:00 {init.sh} /bin/sh /usr/sbin/init.sh
   23 root      0:00 crond
   55 root      0:26 redis-server unixsocket:/tmp/redis.sock
  312 root      0:18 dnscrypt-proxy -config /data/dnscrypt-resolvers/dnscrypt.toml
  337 root      0:03 unbound -c /tmp/unbound_forward.conf -p
  349 root      0:00 {watch_list.sh} /bin/sh /usr/sbin/watch_list.sh
  353 root      0:01 tail -f /dev/null
  386 root      0:22 unbound -c /tmp/unbound_raw.conf -p
 1264 root      0:02 mosdns start -d /data -c /tmp/mosdns.yaml
 1307 root      0:00 inotifywait -e modify,delete /etc/unbound/named.cache /data/Country-only-cn-private.mmdb /data/force_cn_list.txt /data/force_nocn_list.txt /data/custom_env.ini /data/global_mark.dat /data/trackerslist.txt /data/force_forward_list.txt
 1341 root      0:00 sh
 1528 root      0:00 sh
 1534 root      0:00 {debug.sh} /bin/sh /usr/sbin/debug.sh
 1549 root      0:00 ps -ef
*********************************************************************************

[INFO] TOP
*********************************************************************************

CPU:   0% usr   0% sys   0% nic 100% idle   0% io   0% irq   0% sirq
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
  386     1 root     S    2441m  30%   1   0% unbound -c /tmp/unbound_raw.conf -
 1264   349 root     S    1211m  15%   2   0% mosdns start -d /data -c /tmp/mosd
  312     1 root     S    1211m  15%   2   0% dnscrypt-proxy -config /data/dnscr
   55     1 root     S    24232   0%   0   0% redis-server unixsocket:/tmp/redis
  337     1 root     S    21408   0%   2   0% unbound -c /tmp/unbound_forward.co
 1341     0 root     S     1724   0%   1   0% sh
  349     1 root     S     1708   0%   2   0% {watch_list.sh} /bin/sh /usr/sbin/
 1528     0 root     S     1696   0%   3   0% sh
    1     0 root     S     1632   0%   1   0% {init.sh} /bin/sh /usr/sbin/init.s
 1534  1528 root     S     1628   0%   2   0% {debug.sh} /bin/sh /usr/sbin/debug
 1550  1534 root     R     1624   0%   1   0% top -n1
  353     1 root     S     1616   0%   0   0% tail -f /dev/null
 1551  1534 root     S     1612   0%   0   0% grep %
 1307   349 root     S     1072   0%   3   0% inotifywait -e modify,delete /etc/
   23     1 root     S      860   0%   2   0% crond
*********************************************************************************

[INFO] REDIS
*********************************************************************************

used_memory_human:2.47M
used_memory_rss_human:5.92M
used_memory_peak_human:2.47M
total_system_memory_human:7.75G
used_memory_lua_human:31.00K
used_memory_vm_total_human:63.00K
used_memory_scripts_human:181B
maxmemory_human:1.46G
(integer) 3431
*********************************************************************************

[TEST] IP ROUTE
*********************************************************************************

CN IP URL:
223.167.218.122
223.167.218.122
223.167.218.122
CN RAW-IP URL:
223.167.218.122
------------------
Non-CN IP URL:
210.13.100.74
43.247.132.89
43.247.132.89
Non-CN RAW-IP URL:
210.13.100.74
210.13.100.74
210.13.100.74
210.13.100.74
------------------
IP INFO:
210.13.100.74
CN,Shanghai,Shanghai
ASN9929/CHINA UNICOM Industrial Internet Backbone
HTTP/1.1 
Mozilla/5.0 Gecko/20100101 Firefox/120.0 https://github.com/kkkgo/PaoPaoDNS
Asia/Shanghai Time: 11/26/2023, 9:35:18 PM
[INFO] force_cn_list
domain:whoami.ds.akahelp.net
domain:whoami.03k.org
MOSDNS WHOAMI :
akahelp: "ns" "210.13.100.74"
03k: 223.167.218.122
UNBOUND WHOAMI:
akahelp: "ns" "210.13.100.74"
03k: 223.167.218.122
*********************************************************************************

[TEST] HIJACK
*********************************************************************************

;; communications error to 9.8.7.5#53: timed out
;; no servers could be reached

;; communications error to 9.8.7.6#53: timed out
;; no servers could be reached

HIJACK 127.0.0.1 = 58.217.249.139
*********************************************************************************

[TEST] DIG-CN [taobao]
*********************************************************************************

MOSDNS CN:
www.taobao.com.danuoyi.tbcache.com.
112.132.36.204
112.132.36.205
UNBOUND CN:
www.taobao.com.danuoyi.tbcache.com.
112.132.36.205
112.132.36.204
[TEST] DIG-NOCN [youtube]
MOSDNS NOCN:
7.0.0.70
DNSCRYPT-UNBOUND NOCN:
youtube-ui.l.google.com.
142.250.80.110
142.250.176.206
DNSCRYPT NOCN:
youtube-ui.l.google.com.
142.250.68.78
142.250.68.14
DNSCRYPT-SOCKS5 NOCN:
;; communications error to 127.0.0.1#5303: connection refused
;; no servers could be reached

*********************************************************************************

[TEST] DUAL CN [IPv6=YES will have aaaa,taobao]
*********************************************************************************

[TEST] DUAL NOCN [IPv6=YES will block aaaa,youtube]
[TEST] ONLY6 [IPv6=only6 will block aaaa if a ok]
checkipv6.synology.com : ip6.03k.org : 6.ipw.cn : 
*********************************************************************************

[info] ALL TEST FINISH.

Answered by kkkgo

Nov 26, 2023

如果开了ADDINFO功能，在dig的时候，不管是不是FAKEIP，只要有记录，都应该会有预期的addinfo信息说明结果来源。
你可以在dig的时候加上指定的服务器@DNSIP看看，非FAKEIP的结果有可能不是来自PaoPaoDNS。

View full answer

kkkgo · 2023-11-26T13:59:12Z

kkkgo
Nov 26, 2023
Maintainer

如果开了ADDINFO功能，在dig的时候，不管是不是FAKEIP，只要有记录，都应该会有预期的addinfo信息说明结果来源。
你可以在dig的时候加上指定的服务器@DNSIP看看，非FAKEIP的结果有可能不是来自PaoPaoDNS。

4 replies

kkkgo Nov 26, 2023
Maintainer

或者在容器内部dig，和手动设置电脑的DNS试试看。

Dontcampy Nov 26, 2023
Author

找到了一个出问题的域名后，指定paopaodns后正常了。
接着我在华硕路由器排查问题的时候惊讶的发现配置页面上删掉的dnspod地址居然还在。。。应该是破案了，感谢作者回复

kkkgo Nov 26, 2023
Maintainer

可以试试编辑dnsmasq配置文件，指定option 6来直接下发DNS

Dontcampy Nov 26, 2023
Author

改为走这个位置的配置了，ssh去看了下是option 6

hussion · 2023-11-27T07:43:01Z

hussion
Nov 27, 2023

@kkkgo 同遇到这个问题，而且是在PaoPaoDNS自己的容器里测试也会遇到：

容器为macvlan容器，DNS为默认，如下：

8 replies

hussion Nov 27, 2023

好，我把addinfo打开，看看能不能再复现出来

hussion Nov 27, 2023

@kkkgo 调试信息如下：

dig google.com                                                           
                                                                                 
; <<>> DiG 9.18.19 <<>> google.com                                               
;; global options: +cmd                                                          
;; Got answer:                                                                   
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34899                        
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2       
                                                                                 
;; OPT PSEUDOSECTION:                                                            
; EDNS: version: 0, flags:; MBZ: 0x0001, udp: 1232                               
; COOKIE: f3e4a5807c9eae77 (echoed)                                              
;; QUESTION SECTION:                                                             
;google.com.                    IN      A                                        
                                                                                 
;; ANSWER SECTION:                                                               
google.com.             1       IN      A       198.18.0.215                     
                                                                                 
;; ADDITIONAL SECTION:                                                           
20231127160830.762357775.addinfo.paopaodns. 2 IN TXT "Since 4ms From:forward -> 1
92.168.50.88@53"                                                                 
                                                                                 
;; Query time: 38 msec                                                           
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)                                         
;; WHEN: Mon Nov 27 16:08:30 CST 2023                                            
;; MSG SIZE  rcvd: 174

ping google.com                                                          
PING google.com (93.46.8.90): 56 data bytes                                      
^C                                                                               
--- google.com ping statistics ---                                               
9 packets transmitted, 0 packets received, 100% packet loss                      
/data # ping google.com                                                          
PING google.com (93.46.8.90): 56 data bytes                                      
^C                                                                               
--- google.com ping statistics ---                                               
5 packets transmitted, 0 packets received, 100% packet loss

kkkgo Nov 27, 2023
Maintainer

这dig的解析并没有什么问题。198.18.0.215不是你想要的FAKEIP吗？

hussion Nov 27, 2023

不好复现，确定的规律是第一次异常，第二次往后就正常，我是看到容器报错日志才发现

Network error:  https://cdn.staticaly.com/gh/kkkgo/PaoPao-Pref/main/global_mark.dat.sha256sum
2023-11-25 20:59:05 CST
https://cdn.staticaly.com/gh/kkkgo/PaoPao-Pref/main/global_mark.dat.sha256sum
Download failed. Attempting to change the download link...
Network error:  https://cdn.jsdelivr.net/gh/kkkgo/PaoPao-Pref/global_mark.dat.sha256sum
2023-11-25 20:59:00 CST
Network error:  https://cdn.jsdelivr.net/gh/kkkgo/PaoPao-Pref/global_mark.dat.sha256sum
2023-11-25 20:58:59 CST
https://cdn.jsdelivr.net/gh/kkkgo/PaoPao-Pref/global_mark.dat.sha256sum
Download failed. Attempting to change the download link...
Network error:  https://raw.githubusercontent.com/kkkgo/PaoPao-Pref/main/global_mark.dat.sha256sum

那ping的结果，为什么总是不是Fakeip？以及这里的网络错误也是确实有问题，梯子本身是没问题的 @kkkgo

kkkgo Nov 27, 2023
Maintainer

需要你贴调试信息debug.sh。

hussion · 2023-11-27T08:39:04Z

hussion
Nov 27, 2023

21 replies

kkkgo Dec 2, 2023
Maintainer

你可以向该项目PR。

hussion Dec 2, 2023

有个点不太理解，既然上游dnscrypt这么难链接，而且前面也已经通过域名集和本地dns解析后的ip先做过判断了，这时候为何不直接当成被墙流量forward到远程解析呢？为何还要用socks5进行辅助dns查询呢？

kkkgo Dec 2, 2023
Maintainer

custom_forward功能只是自定义转发。转发之后流量怎么走并没有限定的使用方式。

kkkgo Dec 2, 2023
Maintainer

如果你是fakeip，本来就是远程解析。而且前面也解释过AUTO_FORWARD_CHECK的作用了，你想直接forward可以关闭AUTO_FORWARD_CHECK。如果再有其他疑问，可以重新开帖。

hussion Dec 2, 2023

好，感谢解答，可能是我没表述清楚，晚点我重新整理下再新开贴吧

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

搭配PaoPaoGateway访问USE_MARK_DATA中的域名时偶尔不会返回FAKEIP #74

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 33 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

搭配PaoPaoGateway访问USE_MARK_DATA中的域名时偶尔不会返回FAKEIP #74

PaoPaoDNS部署配置

PaoPaoGateway配置

PaoPaoDNS debug.sh

Replies: 3 comments · 33 replies

kkkgo Nov 26, 2023 Maintainer

kkkgo Nov 26, 2023 Maintainer

Dontcampy Nov 26, 2023 Author

kkkgo Nov 26, 2023 Maintainer

Dontcampy Nov 26, 2023 Author

kkkgo Nov 27, 2023 Maintainer

kkkgo Nov 27, 2023 Maintainer

kkkgo Dec 2, 2023 Maintainer

kkkgo Dec 2, 2023 Maintainer

kkkgo Dec 2, 2023 Maintainer

Replies: 3 comments 33 replies

kkkgo
Nov 26, 2023
Maintainer

kkkgo Nov 26, 2023
Maintainer

Dontcampy Nov 26, 2023
Author

kkkgo Nov 26, 2023
Maintainer

Dontcampy Nov 26, 2023
Author

kkkgo Nov 27, 2023
Maintainer

kkkgo Nov 27, 2023
Maintainer

kkkgo Dec 2, 2023
Maintainer

kkkgo Dec 2, 2023
Maintainer

kkkgo Dec 2, 2023
Maintainer