1.5.0 加入的 FakeDNS 改进相关疑问 #1112

KobeArthurScofield · 2022-06-18T11:10:22Z

KobeArthurScofield
Jun 18, 2022

浏览过更新记录发现 1.5.0 在 #731 引入了 fakedns+others Sniffer 及 FakeDNS Pools （多 FakeDNS 池可于 FakeDNSObject 配置为数组）。

现有的疑问是：

将 "destOverride" 配置为 ["fakedns+others"] 是否会和 ["http", "tls", "fakedns"] （1.5.6 后为 ["http", "tls", "quic", "fakedns"] ）完全等价？
在 v2rayNG 1.7.8 (Xray-core1.5.5) 中用自定义配置文件的方式配置 FakeIP 池：
```
"fakedns": [
    {
        "ipPool": "198.18.0.0/15",
        "poolSize": 32768
    },
    {
        "ipPool": "2001:2::/48",
        "poolSize": 32768
    },
]
```
可以使用，但会导致偶尔的首次访问延迟比下方配置延迟明显变大（使用下方配置时体验良好）：
```
"fakedns": {
    "ipPool": "198.18.0.0/15",
    "poolSize": 65536
}
```
配置中 DNS 查询策略为 "queryStrategy": "UseIP" 。是否在多池或者 IPv4 / IPv6 双池的情况下访问会因为 IPv6 FakeIP 池的原因引发超时回退？（仅 IPv6 FakeIP 池可以运行但是会导致连接错误（相关日志在下方），但单 IPv4 FakeIP 池并不会影响最终对 IPv6 地址的访问）

KobeArthurScofield · 2022-06-18T13:15:53Z

KobeArthurScofield
Jun 18, 2022
Author

根据在 v2rayNG 上仅 IPv6 FakeIP 池的测试结果看似乎是因为 FakeDNS 没有返回 IPv6 FakeIP 而是空解析。
不清楚是因为这部分被改动过还是架构特有问题还是 Xray-core 的处理没做好。

06-01 18:50:39.811 I/GoLog   ( 6908): new core
06-01 18:50:39.818 I/GoLog   ( 6908): [Debug] app/log: Logger started
06-01 18:50:39.888 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for mdns.ldns:5353
06-01 18:50:39.889 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for llmnr.ldns:5355
06-01 18:50:39.889 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for 127.0.0.1:10853
06-01 18:50:39.924 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for dnspod.pdns:53
06-01 18:50:39.924 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for dns.google:53
06-01 18:50:39.967 I/GoLog   ( 6908): [Info] app/dns: DNS: created UDP client initialized for dns-unfiltered.adguard.com:53
06-01 18:50:40.009 I/GoLog   ( 6908): [Debug] app/router: MphDomainMatcher is enabled for 2 domain rule(s)
06-01 18:50:40.009 I/GoLog   ( 6908): [Debug] app/router: MphDomainMatcher is enabled for 16 domain rule(s)
06-01 18:50:40.080 I/GoLog   ( 6908): start core
06-01 18:50:40.080 I/GoLog   ( 6908): [Debug] app/router: MphDomainMatcher is enabled for 30050 domain rule(s)
06-01 18:50:40.081 I/GoLog   ( 6908): [Debug] app/proxyman/inbound: creating stream worker on 127.0.0.1:10808
06-01 18:50:40.081 I/GoLog   ( 6908): [Debug] app/proxyman/inbound: creating stream worker on 127.0.0.1:10809
06-01 18:50:40.081 I/GoLog   ( 6908): [Debug] app/proxyman/inbound: creating stream worker on 127.0.0.1:10853
06-01 18:50:40.084 I/GoLog   ( 6908): [Info] transport/internet/tcp: listening TCP on 127.0.0.1:10853
06-01 18:50:40.084 I/GoLog   ( 6908): [Info] transport/internet/udp: listening UDP on 127.0.0.1:10853
06-01 18:50:40.084 I/GoLog   ( 6908): [Info] transport/internet/tcp: listening TCP on 127.0.0.1:10808
06-01 18:50:40.084 I/GoLog   ( 6908): [Info] transport/internet/udp: listening UDP on 127.0.0.1:10808
06-01 18:50:40.084 I/GoLog   ( 6908): [Info] transport/internet/tcp: listening TCP on 127.0.0.1:10809
06-01 18:50:40.084 I/GoLog   ( 6908): [Warning] core: Xray 1.5.5 started
06-01 18:50:40.119 D/com.v2ray.ang( 6908): [/data/app/~~dAYeVzmPrKHwLAP1v8fulw==/com.v2ray.ang-Zc7UlLGFn4i8D60aXlbYKA==/lib/arm64/libtun2socks.so, --netif-ipaddr, 26.26.26.2, --netif-netmask, 255.255.255.252, --socks-server-addr, 127.0.0.1:10808, --tunmtu, 1500, --sock-path, sock_path, --enable-udprelay, --loglevel, notice, --dnsgw, 127.0.0.1:10853]
06-01 18:50:40.121 D/com.v2ray.ang( 6908): Process[pid=18689, hasExited=false]
06-01 18:50:40.121 D/com.v2ray.ang( 6908): /data/user/0/com.v2ray.ang/files/sock_path
06-01 18:50:40.152 I/tun2socks(18689): NOTICE(tun2socks): initializing BadVPN tun2socks 1.999.130
06-01 18:50:40.172 D/com.v2ray.ang( 6908): sendFd tries: 0
06-01 18:50:40.173 I/tun2socks(18689): NOTICE(tun2socks): entering event loop
06-01 18:50:40.454 I/GoLog   ( 6908): [Debug] [1931908086] proxy/dokodemo: processing connection from: 127.0.0.1:43195
06-01 18:50:40.454 I/GoLog   ( 6908): [Info] [1931908086] proxy/dokodemo: received request for 127.0.0.1:43195
06-01 18:50:40.454 I/GoLog   ( 6908): [Info] [1931908086] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:40.454 I/GoLog   ( 6908): [Info] [1931908086] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:40.456 I/GoLog   ( 6908): [Debug] app/dns: domain portal.fb.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:40.456 I/GoLog   ( 6908): [Debug] app/dns: domain portal.fb.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:40.456 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: portal.fb.com -> []
06-01 18:50:40.456 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain portal.fb.com at server FakeDNS > empty response
06-01 18:50:40.505 I/GoLog   ( 6908): [Info] [2397493937] proxy/socks: TCP Connect request to tcp:172.253.113.188:5228
06-01 18:50:40.505 I/GoLog   ( 6908): Not Using Prepared: tcp,172.253.113.188:5228
06-01 18:50:40.505 I/GoLog   ( 6908): [Info] [2397493937] app/dispatcher: default route for tcp:172.253.113.188:5228
06-01 18:50:40.505 I/GoLog   ( 6908): [Info] [2397493937] proxy/freedom: opening connection to tcp:172.253.113.188:5228
06-01 18:50:40.505 I/GoLog   ( 6908): [Info] [2397493937] transport/internet/tcp: dialing TCP to tcp:172.253.113.188:5228
06-01 18:50:40.529 I/GoLog   ( 6908): Not Using Prepared: tcp,172.217.163.42:443
06-01 18:50:40.530 I/GoLog   ( 6908): [Info] [2784171955] proxy/socks: TCP Connect request to tcp:172.217.163.42:443
06-01 18:50:40.530 I/GoLog   ( 6908): [Info] [2784171955] app/dispatcher: default route for tcp:172.217.163.42:443
06-01 18:50:40.530 I/GoLog   ( 6908): [Info] [2784171955] proxy/freedom: opening connection to tcp:172.217.163.42:443
06-01 18:50:40.530 I/GoLog   ( 6908): [Info] [2784171955] transport/internet/tcp: dialing TCP to tcp:172.217.163.42:443
06-01 18:50:40.705 I/GoLog   ( 6908): [Debug] [1474270703] proxy/dokodemo: processing connection from: 127.0.0.1:44451
06-01 18:50:40.705 I/GoLog   ( 6908): [Info] [1474270703] proxy/dokodemo: received request for 127.0.0.1:44451
06-01 18:50:40.705 I/GoLog   ( 6908): [Info] [1474270703] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:40.705 I/GoLog   ( 6908): [Info] [1474270703] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:40.706 I/GoLog   ( 6908): [Debug] app/dns: domain outlook.office365.com will use DNS in order: [FakeDNS UDP:DNSPOD.PDNS:53 TCPL//dnspod.pdns:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:40.706 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: outlook.office365.com -> []
06-01 18:50:40.706 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain outlook.office365.com at server FakeDNS > empty response
06-01 18:50:40.750 I/GoLog   ( 6908): [Debug] [2582644787] proxy/dokodemo: processing connection from: 127.0.0.1:42624
06-01 18:50:40.750 I/GoLog   ( 6908): [Info] [2582644787] proxy/dokodemo: received request for 127.0.0.1:42624
06-01 18:50:40.750 I/GoLog   ( 6908): [Info] [2582644787] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:40.750 I/GoLog   ( 6908): [Info] [2582644787] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:40.750 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:40.750 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:40.750 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: api-stream.twitter.com -> []
06-01 18:50:40.750 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain api-stream.twitter.com at server FakeDNS > empty response
06-01 18:50:41.196 I/GoLog   ( 6908): Not Using Prepared: tcp,198.19.210.157:443
06-01 18:50:41.196 I/GoLog   ( 6908): [Info] [1007857410] proxy/socks: TCP Connect request to tcp:198.19.210.157:443
06-01 18:50:41.197 I/GoLog   ( 6908): [Info] [1007857410] app/dispatcher: taking detour [direct] for [tcp:198.19.210.157:443]
06-01 18:50:41.197 I/GoLog   ( 6908): [Info] [1007857410] proxy/freedom: opening connection to tcp:198.19.210.157:443
06-01 18:50:41.197 I/GoLog   ( 6908): [Info] [1007857410] transport/internet/tcp: dialing TCP to tcp:198.19.210.157:443
06-01 18:50:41.257 I/GoLog   ( 6908): Not Using Prepared: tcp,26.26.26.2:853
06-01 18:50:41.257 I/GoLog   ( 6908): [Info] [2435682276] proxy/socks: TCP Connect request to tcp:26.26.26.2:853
06-01 18:50:41.258 I/GoLog   ( 6908): [Info] [2435682276] app/dispatcher: default route for tcp:26.26.26.2:853
06-01 18:50:41.258 I/GoLog   ( 6908): [Info] [2435682276] proxy/freedom: opening connection to tcp:26.26.26.2:853
06-01 18:50:41.260 I/GoLog   ( 6908): [Info] [2435682276] transport/internet/tcp: dialing TCP to tcp:26.26.26.2:853
06-01 18:50:41.785 I/GoLog   ( 6908): [Debug] [801155121] proxy/dokodemo: processing connection from: 127.0.0.1:38062
06-01 18:50:41.785 I/GoLog   ( 6908): [Info] [801155121] proxy/dokodemo: received request for 127.0.0.1:38062
06-01 18:50:41.785 I/GoLog   ( 6908): [Info] [801155121] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:41.785 I/GoLog   ( 6908): [Info] [801155121] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:41.785 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:41.786 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:41.786 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: api-stream.twitter.com -> []
06-01 18:50:41.786 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain api-stream.twitter.com at server FakeDNS > empty response
06-01 18:50:42.271 I/GoLog   ( 6908): [Info] app/dispatcher: taking detour [proxy] for [tcp:www.google.com:80]
06-01 18:50:42.271 I/GoLog   ( 6908): [Info] transport/internet/websocket: creating connection to tcp:****************:###
06-01 18:50:42.600 I/GoLog   ( 6908): Using Prepared: ###.###.###.###
06-01 18:50:42.907 I/GoLog   ( 6908): [Info] proxy/vmess/outbound: tunneling request to tcp:www.google.com:80 via ***************:###
06-01 18:50:43.835 I/GoLog   ( 6908): [Debug] [349991901] proxy/dokodemo: processing connection from: 127.0.0.1:44825
06-01 18:50:43.835 I/GoLog   ( 6908): [Info] [349991901] proxy/dokodemo: received request for 127.0.0.1:44825
06-01 18:50:43.835 I/GoLog   ( 6908): [Info] [349991901] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:43.835 I/GoLog   ( 6908): [Info] [349991901] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:43.835 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:43.835 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:43.835 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: api-stream.twitter.com -> []
06-01 18:50:43.835 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain api-stream.twitter.com at server FakeDNS > empty response
06-01 18:50:43.837 I/GoLog   ( 6908): [Info] [682561282] app/proxyman/outbound: failed to process outbound traffic > proxy/dns: connection ends > context canceled
06-01 18:50:43.837 I/GoLog   ( 6908): [Info] [682561282] app/proxyman/inbound: connection ends > proxy/dokodemo: connection ends > context canceled
06-01 18:50:44.128 I/GoLog   ( 6908): [Info] [4237362303] app/proxyman/inbound: connection ends > proxy/dokodemo: connection ends > context canceled
06-01 18:50:44.129 I/GoLog   ( 6908): [Info] [513587032] app/proxyman/outbound: failed to process outbound traffic > proxy/dns: connection ends > context canceled
06-01 18:50:44.129 I/GoLog   ( 6908): [Info] [513587032] app/proxyman/inbound: connection ends > proxy/dokodemo: connection ends > proxy/dokodemo: failed to transport response > io: read/write on closed pipe
06-01 18:50:44.129 I/GoLog   ( 6908): [Info] [4237362303] app/proxyman/outbound: failed to process outbound traffic > proxy/dns: connection ends > context canceled
06-01 18:50:47.873 I/GoLog   ( 6908): [Debug] [3770427539] proxy/dokodemo: processing connection from: 127.0.0.1:43825
06-01 18:50:47.874 I/GoLog   ( 6908): [Info] [3770427539] proxy/dokodemo: received request for 127.0.0.1:43825
06-01 18:50:47.874 I/GoLog   ( 6908): [Info] [3770427539] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:47.874 I/GoLog   ( 6908): [Info] [3770427539] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:47.876 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:47.876 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:47.876 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: api-stream.twitter.com -> []
06-01 18:50:47.877 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain api-stream.twitter.com at server FakeDNS > empty response
06-01 18:50:50.895 I/GoLog   ( 6908): [Debug] [3058882515] proxy/dokodemo: processing connection from: 127.0.0.1:43972
06-01 18:50:50.896 I/GoLog   ( 6908): [Info] [3058882515] proxy/dokodemo: received request for 127.0.0.1:43972
06-01 18:50:50.896 I/GoLog   ( 6908): [Info] [3058882515] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:50.896 I/GoLog   ( 6908): [Info] [3058882515] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:50.896 I/GoLog   ( 6908): [Debug] app/dns: domain na.glbtls.t.co matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:50.896 I/GoLog   ( 6908): [Debug] app/dns: domain na.glbtls.t.co will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:50.896 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: na.glbtls.t.co -> []
06-01 18:50:50.896 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain na.glbtls.t.co at server FakeDNS > empty response
06-01 18:50:54.264 I/GoLog   ( 6908): [Info] app/proxyman/outbound: failed to process outbound traffic > proxy/vmess/outbound: connection ends > context deadline exceeded
06-01 18:50:54.268 D/com.v2ray.ang( 6908): measureV2rayDelay: go.Universe$proxyerror: Get "http://www.google.com/generate_204": context deadline exceeded
06-01 18:50:55.137 I/GoLog   ( 6908): [Info] app/dispatcher: taking detour [proxy] for [tcp:www.google.com:80]
06-01 18:50:55.138 I/GoLog   ( 6908): [Info] transport/internet/websocket: creating connection to tcp:****************:###
06-01 18:50:55.952 I/GoLog   ( 6908): [Debug] [3466097952] proxy/dokodemo: processing connection from: 127.0.0.1:47717
06-01 18:50:55.952 I/GoLog   ( 6908): [Info] [3466097952] proxy/dokodemo: received request for 127.0.0.1:47717
06-01 18:50:55.952 I/GoLog   ( 6908): [Info] [3466097952] app/dispatcher: taking detour [dns-out] for [udp:119.29.29.29:53]
06-01 18:50:55.952 I/GoLog   ( 6908): [Info] [3466097952] proxy/dns: handling DNS traffic to udp:119.29.29.29:53
06-01 18:50:55.952 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com matches following rules: [geosite:gfw(DNS idx:5) geosite:greatfire(DNS idx:5) geosite:gfw(DNS idx:8) geosite:greatfire(DNS idx:8) geosite:gfw(DNS idx:9) geosite:greatfire(DNS idx:9) geosite:gfw(DNS idx:10) geosite:greatfire(DNS idx:10) geosite:gfw(DNS idx:11) geosite:greatfire(DNS idx:11)]
06-01 18:50:55.953 I/GoLog   ( 6908): [Debug] app/dns: domain api-stream.twitter.com will use DNS in order: [FakeDNS UDP:DNS.GOOGLE:53 TCP//dns.google:53 UDP:DNS-UNFILTERED.ADGUARD.COM:53 TCP//dns-unfiltered.adguard.com:53]
06-01 18:50:55.953 I/GoLog   ( 6908): [Info] app/dns: FakeDNS got answer: api-stream.twitter.com -> []
06-01 18:50:55.953 I/GoLog   ( 6908): [Info] app/dns: failed to lookup ip for domain api-stream.twitter.com at server FakeDNS > empty response

0 replies

chika0801 · 2022-08-07T11:11:01Z

chika0801
Aug 7, 2022

#1174

联动一下，今天测试了下fakedns+others，遇到的这个问题

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

1.5.0 加入的 FakeDNS 改进相关疑问 #1112

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments

{{title}}

{{title}}

Select a reply

1.5.0 加入的 FakeDNS 改进相关疑问 #1112

KobeArthurScofield Jun 18, 2022

Replies: 2 comments

KobeArthurScofield Jun 18, 2022 Author

chika0801 Aug 7, 2022

KobeArthurScofield
Jun 18, 2022

KobeArthurScofield
Jun 18, 2022
Author

chika0801
Aug 7, 2022