Hi Andrea, I can confirm this behavior. When I ping openoffice.org, the IP changes every second try:
$ ping openoffice.org PING openoffice.org (88.198.26.2) 56(84) bytes of data. ^C --- openoffice.org ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9219ms $ ping openoffice.org PING openoffice.org (140.211.11.105) 56(84) bytes of data. 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=1 ttl=42 time=178 ms 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=2 ttl=42 time=178 ms 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=3 ttl=42 time=180 ms 64 bytes from themis.apache.org (140.211.11.105): icmp_seq=4 ttl=42 time=177 ms ^C --- openoffice.org ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3003ms rtt min/avg/max/mdev = 177.699/178.769/180.838/1.331 ms 88.198.26.2 is unreachable, 140.211.11.105 works as expected. Regards, Matthias Am 07.01.2018 um 01:02 schrieb Andrea Pescetti: > On 05/01/2018 Dave Fisher wrote: >> See the IP Addresses and if they are on the same continent as you >> when you have trouble. See if the trace route has high latency. > > Thanks, this will indeed help a lot in troubleshooting and I have > interesting results: > > $ wget it.openoffice.org > http://it.openoffice.org/ > Resolving it.openoffice.org (it.openoffice.org)... 88.198.26.2, > 140.211.11.105, 2a01:4f8:130:2192::2 > Connecting to it.openoffice.org (it.openoffice.org)|88.198.26.2|:80... > failed: Connection timed out. > Connecting to it.openoffice.org > (it.openoffice.org)|140.211.11.105|:80... connected. > [ and then the download occurs normally ] > > So basically the first choice for me is 88.198.26.2 and that one times > out. > > For some reason, > $ traceroute www.openoffice.org > always picks up 140.211.11.105 so it works fast. > > But if I run > $ traceroute it.openoffice.org > it gets lost somewhere in the Hetzner network in Germany: > > $ traceroute it.openoffice.org > traceroute to it.openoffice.org (88.198.26.2), 30 hops max, 60 byte > packets > 1 [irrelevant local network, omitted] ... > 7 ae3-1.fra20.core-backbone.com (80.81.192.187) 36.559 ms 58.253 > ms 57.011 ms > 8 ae1-2014.nbg40.core-backbone.com (81.95.15.206) 49.496 ms 48.844 > ms 45.724 ms > 9 core-backbone-100g-nbg.hetzner.de (81.95.15.6) 43.109 ms 44.708 > ms 45.224 ms > 10 core12.nbg1.hetzner.com (213.239.229.165) 48.203 ms > core11.nbg1.hetzner.com (213.239.229.161) 48.010 ms 43.750 ms > 11 core21.fsn1.hetzner.com (213.239.245.222) 49.932 ms > core21.fsn1.hetzner.com (213.239.224.14) 57.115 ms 55.405 ms > 12 ex9k1.dc4.fsn1.hetzner.com (213.239.229.146) 52.779 ms 51.393 ms > 57.072 ms > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > ... > 30 * * * > > I think this shows that indeed we need someone to check that DNS record. > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
smime.p7s
Description: S/MIME Cryptographic Signature
