NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
On Wed, Jul 22, 2026 at 05:39:37PM +0000, Jeremy C. Reed wrote:
> What does this mean? Asks for A and AAAA addresses? So the "A" has answer
> and the "AAAA" does not, and since at least one has an address the local
> resolver doesn't retry using the local domain appended? And since you you
> required -6 it fails immediately (on Linux)?
Precisely.
> Back to NetBSD, see resolv.conf(5) already documents this behavior
Can you please pin point? I searched by the word IPv6 in the man page and
could not find the resolution sequence (vary the IP protocol first or
suffixes first).
I notice (using tcpdump) that Linux varies IPv first and NetBSD suffix
first and find the former to be relatively safer.
--
Mayuresh
- References:
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
- Re: After enabling IPv6 curl github.com fails, succeeds with IPv4
Home |
Main Index |
Thread Index |
Old Index