openstreetmap / operations

OSMF Operations Working Group issue tracking
https://operations.osmfoundation.org/
99 stars 12 forks source link

www.openstreetmap.org has AAAA records in DNS but they do not work #482

Closed gozdal closed 3 years ago

gozdal commented 3 years ago

www.openstreetmap.org has AAAA records in the DNS:

root@fritz:~# nslookup www.openstreetmap.org
Server:         172.31.42.8
Address:        172.31.42.8#53

Name:      www.openstreetmap.org
Address 1: 130.117.76.13
Address 2: 130.117.76.11
Address 3: 130.117.76.12
Address 4: 2001:978:2:2c::172:c
Address 5: 2001:978:2:2c::172:d
Address 6: 2001:978:2:2c::172:b

Fetching with IPv4 works:

root@fritz:~# wget -4 www.openstreetmap.org
--2020-12-14 12:13:25--  http://www.openstreetmap.org/
Resolving www.openstreetmap.org... 130.117.76.12, 130.117.76.11, 130.117.76.13
Connecting to www.openstreetmap.org|130.117.76.12|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.openstreetmap.org/ [following]
--2020-12-14 12:13:25--  https://www.openstreetmap.org/
Connecting to www.openstreetmap.org|130.117.76.12|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'

index.html                                              [ <=>                                                                                                                ]  14.45K  --.-KB/s    in 0.04s

Fetching with IPv6 times out:

root@fritz:~# wget -6 www.openstreetmap.org
URL transformed to HTTPS due to an HSTS policy
--2020-12-14 12:13:32--  https://www.openstreetmap.org/
Resolving www.openstreetmap.org... 2001:978:2:2c::172:b, 2001:978:2:2c::172:d, 2001:978:2:2c::172:c
Connecting to www.openstreetmap.org|2001:978:2:2c::172:b|:443...
tomhughes commented 3 years ago

The addresses are valid and reachable:

Start: 2020-12-14T12:53:50+0000
HOST: bericote.compton.nu                               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- gosford.compton.nu                                 0.0%    10    0.9   0.6   0.4   1.0   0.2
  2.|-- s.gormless.thn.aa.net.uk                          10.0%    10    7.3   7.6   6.9  10.5   1.1
  3.|-- ntt.a.needless.tch.aa.net.uk                       0.0%    10    7.4   7.4   7.0   7.7   0.2
  4.|-- xe-0-1-0-3-1.r04.londen05.uk.bb.gin.ntt.net        0.0%    10    8.1   8.4   7.9   9.8   0.6
  5.|-- ae-7.r20.londen12.uk.bb.gin.ntt.net                0.0%    10    8.1   8.4   7.9   9.2   0.4
  6.|-- ae-8.r02.londen03.uk.bb.gin.ntt.net                0.0%    10    8.3   8.4   7.9   8.8   0.3
  7.|-- 2001:728:0:4000::7e                               20.0%    10    8.2   8.2   7.9   8.5   0.2
  8.|-- ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- be12488.ccr42.ams03.atlas.cogentco.com            70.0%    10   15.4  15.7  15.4  16.0   0.3
 10.|-- be2440.agr21.ams03.atlas.cogentco.com              0.0%    10   15.3  15.5  14.9  15.8   0.3
 11.|-- te0-0-2-0.nr11.b059546-0.ams03.atlas.cogentco.com  0.0%    10   16.5  16.1  15.7  16.5   0.2
 12.|-- 2001:978:2:2c::172:b                               0.0%    10   15.3  15.3  15.1  15.7   0.2

If you are unable to reach them then it's a routing issue that you would need to address with your network provider. Certainly there's nothing we can do to help.

Of course it's quite likely that it's not your provider either but some third party network in the middle that neither of us has any influence over.

gozdal commented 3 years ago

I'm connected via Hurricane Electric and have otherwise no problem with IPv6 connectivity. Maybe that's something that should be brought up with your provider (Cogent I guess)?

westnordost commented 3 years ago

Sure it is a problem of the provider of the client? Same for me, using popular provider in Hamburg, nothing fringe.

>ping -6 openstreetmap.org
Ping request could not find host openstreetmap.org. Please check the name and try again.

>ping -4 openstreetmap.org

Pinging openstreetmap.org [130.117.76.11] with 32 bytes of data:
Reply from 130.117.76.11: bytes=32 time=29ms TTL=51
Reply from 130.117.76.11: bytes=32 time=29ms TTL=51

Edit: on the other hand....:

>ping -6 www.google.de
Ping request could not find host www.google.de. Please check the name and try again.
tomhughes commented 3 years ago

There is a well known battle between HE and Cogent that means connections between them can be unreliable.

gozdal commented 3 years ago

It seems it's a known issue https://www.reddit.com/r/ipv6/comments/azyt57/just_ran_into_a_cogent_not_peering_with_hurricane/ :/

mnalis commented 3 years ago

Yes, Cogent - HurricaneElectric battle is annoying as hell. If one has their own AS, one possible workaround is to peer with both (HE provides free BGP peering at https://tunnelbroker.net). Alternatively, there is talk that OSM might be starting using some external CDNs, will that be solving this issue?