Нашёл адрес, который с моей нынешней виртуалки доступен, а с будущей нет:
$ ssh phdru.name sudo tcptraceroute ns2.trifle.net 53
Running:
traceroute -T -O info -p 53 ns2.trifle.net
traceroute to ns2.trifle.net (195.24.156.218), 30 hops max, 60 byte packets
1 * * *
2 10.82.68.45 (10.82.68.45) 0.822 ms 10.82.68.55 (10.82.68.55) 0.801 ms 10.82.68.61 (10.82.68.61) 0.914 ms
3 138.197.250.118 (138.197.250.118) 1.382 ms 138.197.250.110 (138.197.250.110) 1.145 ms 138.197.250.102 (138.197.250.102) 1.434 ms
4 138.197.250.92 (138.197.250.92) 1.271 ms 138.197.250.74 (138.197.250.74) 0.954 ms 138.197.250.94 (138.197.250.94) 1.083 ms
5 * * ams-equ-cr1.ae113-2776.rascom.as20764.net (80.64.108.32) 1.121 ms
6 * * *
7 80.64.98.225.rascom.as20764.net (80.64.98.225) 57.928 ms 57.737 ms 57.927 ms
8 88.81.244.34 (88.81.244.34) 48.489 ms 88.81.244.42 (88.81.244.42) 45.517 ms 45.477 ms
9 * * *
10 195.24.128.75 (195.24.128.75) 54.524 ms 54.534 ms 54.469 ms
11 ns2.trifle.net (195.24.156.218) <syn,ack> 53.034 ms 52.823 ms 53.701 ms
$ ssh 194.87.140.76 sudo tcptraceroute ns2.trifle.net 53
Running:
traceroute -T -O info -p 53 ns2.trifle.net
traceroute to ns2.trifle.net (195.24.156.218), 30 hops max, 60 byte packets
1 gw.node (194.147.115.1) 13.892 ms 8.786 ms 14.589 ms
2 185.15.209.28 (185.15.209.28) 2.204 ms 2.214 ms 2.007 ms
3 ae2-225.RT.SRV.MEP.NL.retn.net (87.245.236.176) 5.098 ms 5.044 ms 4.987 ms
4 ae0-9.RT.BMB.KIV.UA.retn.net (87.245.232.151) 52.616 ms 52.695 ms 52.719 ms
5 GW-DataGroup.retn.net (87.245.247.13) 53.357 ms 52.698 ms 52.644 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
Обе виртуалки в Амстердаме. Сейчас этот адрес важен — много лет был моим вторичным DNS. В будущем уже не будет. Но всё-таки это как-то неправильно.
$ ssh phdru.name host phdru.name ns2.trifle.net
Using domain server:
Name: ns2.trifle.net
Address: 195.24.156.218#53
Aliases:
phdru.name has address 188.166.106.171
$ ssh 194.87.140.76 host phdru.name ns2.trifle.net
;; connection timed out; no servers could be reached
X-Post в ЖЖ.
$ ssh phdru.name sudo tcptraceroute ns2.trifle.net 53
Running:
traceroute -T -O info -p 53 ns2.trifle.net
traceroute to ns2.trifle.net (195.24.156.218), 30 hops max, 60 byte packets
1 * * *
2 10.82.68.45 (10.82.68.45) 0.822 ms 10.82.68.55 (10.82.68.55) 0.801 ms 10.82.68.61 (10.82.68.61) 0.914 ms
3 138.197.250.118 (138.197.250.118) 1.382 ms 138.197.250.110 (138.197.250.110) 1.145 ms 138.197.250.102 (138.197.250.102) 1.434 ms
4 138.197.250.92 (138.197.250.92) 1.271 ms 138.197.250.74 (138.197.250.74) 0.954 ms 138.197.250.94 (138.197.250.94) 1.083 ms
5 * * ams-equ-cr1.ae113-2776.rascom.as20764.net (80.64.108.32) 1.121 ms
6 * * *
7 80.64.98.225.rascom.as20764.net (80.64.98.225) 57.928 ms 57.737 ms 57.927 ms
8 88.81.244.34 (88.81.244.34) 48.489 ms 88.81.244.42 (88.81.244.42) 45.517 ms 45.477 ms
9 * * *
10 195.24.128.75 (195.24.128.75) 54.524 ms 54.534 ms 54.469 ms
11 ns2.trifle.net (195.24.156.218) <syn,ack> 53.034 ms 52.823 ms 53.701 ms
$ ssh 194.87.140.76 sudo tcptraceroute ns2.trifle.net 53
Running:
traceroute -T -O info -p 53 ns2.trifle.net
traceroute to ns2.trifle.net (195.24.156.218), 30 hops max, 60 byte packets
1 gw.node (194.147.115.1) 13.892 ms 8.786 ms 14.589 ms
2 185.15.209.28 (185.15.209.28) 2.204 ms 2.214 ms 2.007 ms
3 ae2-225.RT.SRV.MEP.NL.retn.net (87.245.236.176) 5.098 ms 5.044 ms 4.987 ms
4 ae0-9.RT.BMB.KIV.UA.retn.net (87.245.232.151) 52.616 ms 52.695 ms 52.719 ms
5 GW-DataGroup.retn.net (87.245.247.13) 53.357 ms 52.698 ms 52.644 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
Обе виртуалки в Амстердаме. Сейчас этот адрес важен — много лет был моим вторичным DNS. В будущем уже не будет. Но всё-таки это как-то неправильно.
$ ssh phdru.name host phdru.name ns2.trifle.net
Using domain server:
Name: ns2.trifle.net
Address: 195.24.156.218#53
Aliases:
phdru.name has address 188.166.106.171
$ ssh 194.87.140.76 host phdru.name ns2.trifle.net
;; connection timed out; no servers could be reached
X-Post в ЖЖ.