Question

从过去几天开始，网站上的流量（https://www.fanspole.com/）过高，因此我们正在尝试优化网站。我注意到的一件事是DNS解析时间太长了..

@MacBook-Air ~ $ ping fanspole.com
PING fanspole.com (139.162.35.126): 56 data bytes
64 bytes from 139.162.35.126: icmp_seq=0 ttl=56 time=717.688 ms
64 bytes from 139.162.35.126: icmp_seq=1 ttl=56 time=606.560 ms
64 bytes from 139.162.35.126: icmp_seq=2 ttl=56 time=654.942 ms
64 bytes from 139.162.35.126: icmp_seq=3 ttl=56 time=677.301 ms
64 bytes from 139.162.35.126: icmp_seq=4 ttl=56 time=699.991 ms
Request timeout for icmp_seq 5
64 bytes from 139.162.35.126: icmp_seq=6 ttl=56 time=601.355 ms
64 bytes from 139.162.35.126: icmp_seq=7 ttl=56 time=660.974 ms
64 bytes from 139.162.35.126: icmp_seq=8 ttl=56 time=605.084 ms
--- fanspole.com ping statistics ---
10 packets transmitted, 8 packets received, 20.0% packet loss
round-trip min/avg/max/stddev = 601.355/652.987/717.688/42.087 ms

我们现在正在使用Linode DNS Manager。有人可以提出更好的选择。

Answer 1

这是不 DNS解析问题，是网络拥塞问题。

traceroute to 139.162.35.126 (139.162.35.126), 30 hops max, 60 byte packets <internal hops removed> 4 10gigabitethernet5-1.core1.lon1.he.net (5.57.80.128) 22.367 ms 22.618 ms 22.841 ms 5 10ge2-9.core1.lon2.he.net (72.52.92.222) 24.056 ms 24.277 ms 24.500 ms 6 100ge1-1.core1.nyc4.he.net (72.52.92.166) 94.769 ms 93.549 ms 93.694 ms 7 100ge14-2.core1.sjc2.he.net (184.105.81.213) 156.692 ms 147.815 ms 147.974 ms 8 * * * 9 * * * 10 xe0-2-0.gw1.sin2.pacnet.net (202.147.52.66) 320.731 ms 321.978 ms 321.950 ms 11 * * * 12 139.162.0.10 (139.162.0.10) 252.825 ms 251.826 ms 251.285 ms 13 li1448-126.members.linode.com (139.162.35.126) 251.746 ms 252.270 ms 251.406 ms

这是一个来自英国伦敦的追踪路线 - 你可以在第7行看到它点击he.net它开始捡起延迟。当它在pacnet.net的第10行到达其300 + ms

时

此处唯一的选择是迁移到不同的Linode地区或不同的托管服务提供商，提供更好/更少拥塞的网络链接。

DNS管理的最佳选择

1 个答案: