Yes, unfortunately, I don't have control over the app(NPM) in NodeJS that
is making the call. A bit of a chicken and the egg problem since they
didn't make it the default...
On Tue, May 1, 2018 at 7:21 PM, Mark Andrews wrote:
> Upgrading nodejs and getting verbatim=1 added to the appropriate cal
Upgrading nodejs and getting verbatim=1 added to the appropriate call
should also help. The bug report you linked to showed that getaddrinfo
result order will now be honoured with verbatim=1. You then just need
to ensure that getaddrinfo is correctly configured to return IPv6
addresses before IPv
Yeah, fighting with the application developers doesn't appear to be a good
option, nor is applying any tunneling mechanisms such as 464xlat.
One of the main goals is to establish an ipv6 only network that just works.
An ipv6 only network doesn't need A records. I'll give a link to my patch
or repo
Which is really because they don’t understand that happy eyeballs is
just a tweak to RFC 1123 multi-homed server support. It isn’t IPv6
transition support. It’s just the IPv6 results in a LOT MORE MULTI-HOMED
sites especially when DNS64 is in the mix.
Failure to honour address preferences returne
If you have a IPv6 only network then there should be no default IPv4 route so
the connect(), sendto() etc. should all fail immediately with network
unreachable.
If they don’t then complain to your OS developer. If the application does not
detect these failures complain to the application developer
5 matches
Mail list logo
