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 08:37:13AM +0200, Martin Husemann wrote:
> On Wed, Jul 22, 2026 at 12:02:33PM +0530, Mayuresh wrote:
> > If neither the search option in the /etc/resolv.conf file or the
> > ''LOCALDOMAIN'' environment variable is used, then the search list of
> > domains contains only the full domain specified by the domain option
> > (in /etc/resolv.conf) or the domain used in the local hostname
>
> And this is exactly what happens with NetBSD too.
No. We try github.com.in when the hostname is warunjikar.in. Per above
note, it should have (if at all) only tried github.com.warunjikar.in.
But since github.com is not a non-fqdn, it should not have tried any
alternative at all. This is not written clearly, in FreeBSD or Linux
documents I cited. In either case, neither of the two would extract .in
from my hostname and try appending.
--
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