-
Notifications
You must be signed in to change notification settings - Fork 200
Closed
Description
Hello,
When I'm on an IPv4 network, everything is fine:
$ mix deps.get
Running dependency resolution...
Dependency resolution completed:
poison 3.1.0
* Getting poison (Hex package)
Checking package (https://repo.hex.pm/tarballs/poison-3.1.0.tar)
Fetched package
$
However, when I connect to an IPv6 VPN that does NAT64 for talking with the public internet, I can't install packages:
$ mix deps.get
Failed to fetch record for 'poison' from registry (using cache)
{:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]}
Running dependency resolution...
Dependency resolution completed:
poison 3.1.0
All dependencies up to date
$
Without inspecting the code, it seems to me that it explicitly looks for A records in the response, ignoring AAAA records (that are present in the response).
Is it intended to not work in such IPv6 scenarios?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels