Has anyone tried using BOINC in a NAT64+DNS64 network? I've moved my laptop to such network (after previously using it in IPv4-only and dual-stack Internet-connected networks), and nothing seems to work - boincstats BAM won't connect (fails with Account manager RPC failed: transient HTTP error), projects won't connect (tried LHC@home, RNA World and climateprediction.net, all fail with Scheduler request failed: Server returned nothing (no headers, no data).)

BOINC 7.6.34 on macOS 10.12.6

Dev guide: https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html

Long story short:

IPv4-only servers must be accessed via hostname. The translated address from the 64:ff9b::/96 prefix is provided by the DNS64 server (using google's 2001:4860:4860::6464)
IPv4 literals won't work, use high-level APIs that will work with either IPv4 and IPv6

I don't know, so I forwarded your question to the BOINC development email list. Let's see what kind of answers come in.

---

Ran Wireshark and sure enough - there are DNS queries going out for rnaworld.de and bam.boincstats.com, but the requested record is A, not AAAA.

I read somewhere (had a quick google session), that BOINC uses its own DNS resolver - is that (still) true? That's where the problem most likely is.

@Devs: If you don't have access to proper NAT64, macOS can be used to create such a network (System Preferences -> Sharing -> Internet) since 10.11 I believe (see link to guidelines in the OP). There is a small difference (all DNS queries from the client are changed to A queries to upstream DNS, so all connections use NAT64), though that shouldn't make a difference as long as the servers are available via IPv4.

BOINC uses libcurl to handle its connections to outside world. The Mac version uses IPv4 only to work around some bug. I asked our Mac developer to take a look if the workaround is still needed.