我的網站只有我一個人無法訪問。tracert找到伺服器，儘管它報告了不同的網域（並且在 23 跳處似乎相當長）。ping有效，引用與tracert相同的IP。nslookup也報告相同的IP。
Web 瀏覽器、ssh 和 sftp 都報告「連線已逾時」。
我在多台電腦上看到同樣的問題（儘管都在同一本本機網路上；Windows 7 和 10）。
我可以連接到主機 (DreamHost) 的控制面板並存取所有常用功能。那裡沒有什麼不正常的。
我可以使用 Lynx 從我在另一個國家可以存取的伺服器上的 shell 控制台瀏覽到網站。網路服務，例如isup.me和衝剪機報告連線站點沒有問題。
在過去的幾個月裡，這種情況已經發生過幾次。半天左右後又可以了。如何縮小實際問題的範圍？
該網站是www.yukongis.ca
Tracert 和 ping 結果（透過 WinMTR）：
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| gateway.mkcd - 0 | 823 | 823 | 0 | 0 | 0 | 0 |
| 10.131.127.254 - 1 | 819 | 818 | 5 | 29 | 502 | 6 |
| 10.11.64.25 - 0 | 822 | 822 | 5 | 23 | 522 | 9 |
| 10.1.2.113 - 1 | 815 | 813 | 31 | 36 | 312 | 33 |
| 64.230.219.141 - 1 | 819 | 818 | 31 | 36 | 310 | 33 |
|tcore4-edmonton_bundle-ether1.net.bell.ca - 1 | 819 | 818 | 48 | 55 | 334 | 52 |
|tcore3-vancouver_tengige0-15-0-5.net.bell.ca - 0 | 822 | 822 | 50 | 55 | 351 | 51 |
|tcore3-seattle_hundredgige0-5-0-0.net.bell.ca - 1 | 819 | 818 | 49 | 53 | 330 | 52 |
| bx4-seattle_ae2.net.bell.ca - 0 | 822 | 822 | 49 | 59 | 540 | 51 |
| 206.111.7.17.ptr.us.xo.net - 1 | 819 | 818 | 49 | 53 | 415 | 53 |
| vb2000d1.rar3.seattle-wa.us.xo.net - 0 | 822 | 822 | 109 | 114 | 409 | 113 |
| ae0.rcb1.saltlake2-ut.us.xo.net - 0 | 822 | 822 | 108 | 112 | 406 | 110 |
| 207.88.12.144.ptr.us.xo.net - 0 | 822 | 822 | 112 | 116 | 408 | 113 |
| 207.88.12.190.ptr.us.xo.net - 1 | 819 | 818 | 111 | 120 | 591 | 116 |
| te0-12-0-0.rar3.sanjose-ca.us.xo.net - 1 | 819 | 818 | 112 | 115 | 417 | 113 |
| 207.88.12.164.ptr.us.xo.net - 0 | 822 | 822 | 111 | 116 | 416 | 114 |
| 207.88.12.213.ptr.us.xo.net - 1 | 819 | 818 | 109 | 118 | 388 | 110 |
| 207.88.12.214.ptr.us.xo.net - 0 | 822 | 822 | 108 | 122 | 406 | 110 |
| 207.88.14.181.ptr.us.xo.net - 0 | 822 | 822 | 110 | 115 | 417 | 113 |
| 209.48.43.58 - 1 | 819 | 818 | 113 | 116 | 392 | 114 |
| ip-208-113-156-4.dreamhost.com - 1 | 819 | 818 | 112 | 115 | 393 | 114 |
| ip-208-113-156-14.dreamhost.com - 0 | 822 | 822 | 111 | 116 | 409 | 113 |
|apache2-argon.thomas-lynch-jr.dreamhost.com - 0 | 822 | 822 | 113 | 116 | 410 | 115 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
輸出nslookup -d2：
------------
SendRequest(), len 42
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
1.1.168.192.in-addr.arpa, type = PTR, class = IN
------------
------------
Got answer (68 bytes):
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
1.1.168.192.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 1.1.168.192.in-addr.arpa
type = PTR, class = IN, dlen = 14
name = gateway.mkcd
ttl = 0 (0 secs)
------------
Server: gateway.mkcd
Address: 192.168.1.1
------------
SendRequest(), len 38
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca.mkcd, type = A, class = IN
------------
------------
Got answer (38 bytes):
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca.mkcd, type = A, class = IN
------------
------------
SendRequest(), len 38
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca.mkcd, type = AAAA, class = IN
------------
------------
Got answer (113 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
www.yukongis.ca.mkcd, type = AAAA, class = IN
AUTHORITY RECORDS:
-> (root)
type = SOA, class = IN, dlen = 64
ttl = 569 (9 mins 29 secs)
primary name server = a.root-servers.net
responsible mail addr = nstld.verisign-grs.com
serial = 2017052801
refresh = 1800 (30 mins)
retry = 900 (15 mins)
expire = 604800 (7 days)
default TTL = 86400 (1 day)
------------
------------
SendRequest(), len 33
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca, type = A, class = IN
------------
------------
Got answer (49 bytes):
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca, type = A, class = IN
ANSWERS:
-> www.yukongis.ca
type = A, class = IN, dlen = 4
internet address = 208.113.218.229
ttl = 12817 (3 hours 33 mins 37 secs)
------------
------------
SendRequest(), len 33
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.yukongis.ca, type = AAAA, class = IN
------------
------------
Got answer (97 bytes):
HEADER:
opcode = QUERY, id = 5, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
www.yukongis.ca, type = AAAA, class = IN
AUTHORITY RECORDS:
-> yukongis.ca
type = SOA, class = IN, dlen = 52
ttl = 445 (7 mins 25 secs)
primary name server = ns1.dreamhost.com
responsible mail addr = hostmaster.dreamhost.com
serial = 2017042704
refresh = 19223 (5 hours 20 mins 23 secs)
retry = 1800 (30 mins)
expire = 1814400 (21 days)
default TTL = 14400 (4 hours)
------------
Name: www.yukongis.ca
Address: 208.113.218.229
答案1
你在你的伺服器上使用類似fail2ban的東西嗎？
至少你的問題看起來像是一種反濫用對策，即如果一個IP嘗試快速連接到伺服器，它將被阻止一段時間。
這也可以解釋為什麼您可以在一段時間後再次連接。
也許您的提供者有類似的東西。那你必須請求他們的支持。
答案2
除了 DNS 問題之外，還可能有其他問題：
防火牆相關：返迴路徑問題（回應來自網站的備用頁面，返回時未透過防火牆 - 可以使用瀏覽器監視器/追蹤器進行追蹤）。這是網站設計中的錯誤，通常由所有者糾正。
路由：您有影響目標 IP 的路由（如 EIGRP 隧道），並且流量是透過隧道路由，而不是直接透過 ISP 退出（可以透過在路由器設定中顯示 IP 路由來檢查）。這可以透過在路由器中新增靜態路由（如果您的公司、ISP 等）來解決。
答案3
聽起來您有本地 DNS 問題。我假設您的意思是每個人（您的人脈之外）都可以訪問該網站，但您除外。然後它指向本地的某個東西。快速檢查是強制更改您的 DNS，因此不要使用本地 DNS，而是使用 8.8.8.8
我假設這個問題的另一個原因是它在一天後解決，大多數 DNS 更新在午夜，因此問題在第二天解決。