1
eveqvq982 275 天前
服务器: dns.lan
Address: 10.16.1.1 非权威应答: 名称: js.aq.qq.com.sched.px.tdnsv6.com.tpic.cdn.chinaidcnet.com Addresses: 183.60.159.86 125.88.186.178 125.88.186.169 125.88.186.204 125.88.186.164 125.88.186.174 183.60.159.94 183.60.159.93 125.88.186.159 125.88.186.168 125.88.186.177 Aliases: js.aq.qq.com js.aq.tc.qq.com js.aq.tcdn.qq.com js.aq.qq.com.sched.px.tdnsv6.com > 200 OK | 151 ms | 6.3 KB * Preparing request to https://js.aq.qq.com/js/aq_common.js * Current time is 2024-02-22T09:02:30.421Z * Enable automatic URL encoding * Using default HTTP version * Enable timeout of 30000ms * Enable SSL validation * Enable cookie sending with jar of 2 cookies * Trying 183.60.159.86:443... * Connected to js.aq.qq.com (183.60.159.86) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS header, Certificate Status (22): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS header, Finished (20): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS header, Certificate Status (22): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS header, Finished (20): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 * ALPN, server accepted to use h2 * Server certificate: * subject: C=CN; ST=Guangdong Province; L=Shenzhen; O=Tencent Technology (Shenzhen) Company Limited; CN=js.aq.qq.com * start date: Dec 18 00:00:00 2023 GMT * expire date: Jan 11 23:59:59 2025 GMT * subjectAltName: host "js.aq.qq.com" matched cert's "js.aq.qq.com" * issuer: C=US; O=DigiCert Inc; CN=DigiCert Secure Site CN CA G3 * SSL certificate verify ok. * Using HTTP2, server supports multiplexing * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (OUT), TLS header, Supplemental data (23): * Using Stream ID: 1 (easy handle 0x1cc8ee2b690) * TLSv1.2 (OUT), TLS header, Supplemental data (23): > GET /js/aq_common.js HTTP/2 > Host: js.aq.qq.com > user-agent: insomnia/2023.5.8 > accept: */* * TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! * TLSv1.2 (OUT), TLS header, Supplemental data (23): * TLSv1.2 (IN), TLS header, Supplemental data (23): * TLSv1.2 (IN), TLS header, Supplemental data (23): < HTTP/2 200 < date: Thu, 22 Feb 2024 09:02:30 GMT < content-type: application/javascript < content-length: 6474 < server: NWS_TCloud_PX < cache-control: max-age=600 < expires: Thu, 22 Feb 2024 09:12:30 GMT < last-modified: Fri, 20 Nov 2020 03:04:31 GMT < x-nws-log-uuid: 43df56dd-040c-4d78-bb03-708fbeb0e57d < access-control-allow-origin: * < x-cache-lookup: Hit From Disktank3 < x-daa-tunnel: hop_count=1 < x-cache-lookup: Hit From Inner Cluster * Received 6.3 KB chunk * TLSv1.2 (IN), TLS header, Supplemental data (23): * Connection #0 to host js.aq.qq.com left intact |
2
cat 275 天前
发帖问的时间,手动改一下 DNS 不是更快吗……
|
3
mytsing520 275 天前
打开 F12 ,看看时间长在哪里
|
4
tlerbao 275 天前
秒开
|
5
tanranran 275 天前
+1.我这也慢
|
6
ae86 275 天前
秒开
|
7
bleem 275 天前
秒开
|
8
xiaoshu 275 天前
应该是路由到腾讯 CAP IP 。有一次只配置了 CAP 入口,导致很慢
|
9
Xusually 275 天前 via iPhone
秒开
|
10
flynaj 275 天前 via Android
是 smartdns ,解析到 1 最快的服务器
|
11
z919126592 274 天前
秒开
|
16
kobeguang OP 各位,我应该是找到问题原因了。
之前在 openwrt 加负载均衡,电信 iptv 的 ip 我用了 125.88.0.0/16 ,本来以为这个网段都是 iptv 的,但其实很多广东电信的正常网络 ip 也在这个网段内,比如我本地访问上面的链接,实际 ip 是 125.88.186.164 。这样就被路由到了 iptv 的 wan ,但 iptv 的 wan 是不能访问外网的。所以出现了一连串类似问题 |