之前在坛子里收了一台年抛一折hytron，最近才开始用，发现即使是apt update这种操作也会卡顿，尝试了一下ping google.com，会出现这种情况：

root@localhost:~# ping google.comPING google.com(nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e)) 56 data bytes64 bytes from nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e): icmp_seq=1 ttl=252 time=0.834 ms64 bytes from nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e): icmp_seq=2 ttl=252 time=0.863 ms64 bytes from nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e): icmp_seq=3 ttl=252 time=0.952 ms64 bytes from nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e): icmp_seq=4 ttl=252 time=0.956 ms64 bytes from nchkga-am-in-x0e.1e100.net (2404:6800:4005:823::200e): icmp_seq=5 ttl=252 time=0.909 ms^C--- google.com ping statistics ---5 packets transmitted, 5 received, 0% packet loss, time 22031msrtt min/avg/max/mdev = 0.834/0.902/0.956/0.048 ms

虽然每次发包都很正常，但是总用时22秒才发了5次包，已经dd了纯净的debian12，dns服务器是1.1.1.1，改成8.8.8.8也还是这样。
如果加上-n参数ping -n google.com，关闭反向dns查询，就正常，所以去试了一下dig google.com @1.1.1.1
经常出现communications error to 1.1.1.1#53: timed out：

root@localhost:~# dig google.com @1.1.1.1;; communications error to 1.1.1.1#53: timed out; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> google.com @1.1.1.1;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52175;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 1232;; QUESTION SECTION:;google.com.                    IN      A;; ANSWER SECTION:google.com.             297     IN      A       172.253.62.113google.com.             297     IN      A       172.253.62.139google.com.             297     IN      A       172.253.62.138google.com.             297     IN      A       172.253.62.100google.com.             297     IN      A       172.253.62.101google.com.             297     IN      A       172.253.62.102;; Query time: 0 msec;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP);; WHEN: Tue Sep 16 23:06:12 CST 2025;; MSG SIZE  rcvd: 135

几乎可以肯定是dns有点问题了，所以我测试了一下直接ping谷歌的ip，8次发包耗时7秒，也正常：

root@localhost:~# ping 2404:6800:4005:823::200ePING 2404:6800:4005:823::200e(2404:6800:4005:823::200e) 56 data bytes64 bytes from 2404:6800:4005:823::200e: icmp_seq=1 ttl=252 time=1.02 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=2 ttl=252 time=1.02 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=3 ttl=252 time=1.06 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=4 ttl=252 time=1.07 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=5 ttl=252 time=1.01 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=6 ttl=252 time=1.09 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=7 ttl=252 time=1.05 ms64 bytes from 2404:6800:4005:823::200e: icmp_seq=8 ttl=252 time=0.983 ms^C--- 2404:6800:4005:823::200e ping statistics ---8 packets transmitted, 8 received, 0% packet loss, time 7018msrtt min/avg/max/mdev = 0.983/1.037/1.092/0.033 ms

DNS试过1.1.1.1、8.8.4.4、8.8.8.8等都会这样，探针里看cpu占用也一直正常