On Thu, Feb 09, 2023 at 03:00:24AM -0500, gene heskett wrote:
> > This would suggest that the AAAA record for yahoo is available, but the
> > v6 connectivity is not.
> >
> > Show us the result of 'ip addr list' on your box...
> >
> > Cheers
> ip addr list.{Munged}
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether munged brd ff:ff:ff:ff:ff:ff
> altname enp0s31f6
> inet munged brd munged scope global noprefixroute eno1
> valid_lft forever preferred_lft forever
> inet6 fe80::42b0:76ff:fe5b:113c/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
Thanks. What I see is that the only ipv6 addresses you have are the
"::1/128" on lo (this is the v6 equivalent to the v4 127.0.0.1) and
that "fe80:...", which is a v6 link local address [1]. Your computer
won't get as far as your Ethernet cable with that, so that'd explain
the "no route to host".
This means that your computer isn't getting a viable IPv6 address.
This may sound paradoxical, since "v6 host resolution" is working,
but is not, because both are decoupled: the DNS request/reply is
giving you the A (aka v4) and AAAA (v6) records over ipv4. The
higher layer protocol (DNS) doesn't care what kind the lower layer
(IP) was over which it was transported.
If you care about v6 (or are just curious), you might try to debug
your v6 setup until you get it working or find out that your provider
isn't playing along after all.
You'd start with your local network: that should always be possible.
Then work your way upstream to your router.
Cheers
[1] https://en.wikipedia.org/wiki/Link-local_address#IPv6
--
t
Attachment:
signature.asc
Description: PGP signature