Bug 229538 - svn.freebsd.org not accessible from IPv6-only host
Summary: svn.freebsd.org not accessible from IPv6-only host
Status: Closed FIXED
Alias: None
Product: Services
Classification: Unclassified
Component: Core Infrastructure (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Cluster Admin
URL:
Keywords:
Depends on: 254756
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-05 12:01 UTC by Bengt Ahlgren
Modified: 2021-09-02 05:04 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bengt Ahlgren 2018-07-05 12:01:19 UTC
It is not possible to access svn.freebsd.org from an IPv6-only host.  Only the CNAME record for svn.freebsd.org can be resolved, then it seems stuck.  I don't see any nameserver for geo.freebsd.org with an AAAA record.  Can this be the cause?  Strange enough, "pkg update" etc does work, despite that pkg.freebsd.org, which also uses geo.freebsd.org, also does not resolve.
Comment 1 Gavin Atkinson freebsd_committer freebsd_triage 2018-07-05 12:12:49 UTC
If you're trying to resolve from your host directly (i.e. not sending your DNS traffic to an intermediate resolver like GoogleDNS or your ISP's resolver) then yes, this is likely the cause.

Unfortunately we don't currently have IPv6 addresses on our geo.freebsd.org nameservers.  These nameservers route traffic to your nearest mirror, so that for example if you're in Sweden, we'll likely direct you to the Europe mirror (in Britain) based on the fact your DNS query comes from the Sweden area.  We do this by looking up the geolocation for your IP address, and while the MaxMind database we use is very good for IPv4 geolocation it's pretty disappointing for IPv6 data.  It's a difficult tradeff, but as almost all DNS servers have IPv4 and IPv6 addresses in practice it rarely causes any problems even if it does feel a bit wrong to do this.

I'll test the IPv6 geo data again, and if it's improved significantly will look at v6-enabling at least one of the geo.freebsd.org nameservers.

Thanks,

Gavin
Comment 2 Bengt Ahlgren 2018-07-05 12:25:24 UTC
Yes, that is correct, I'm trying to resolve directly from my host.  I had a local_unbound with no forwarder set, and indeed, it does work if I configure one.

Thanks for the workaround tip and the quick response!