dhcpcd-discuss

Re: Invalid resolv.conf configuration is generated

Timo Sigurdsson

Mon May 27 12:19:58 2019

Hi Bruce,

Bruce Schultz schrieb am 27.05.2019 12:41:

> I'm getting the following line in my resolv.conf file after connecting 
> to my wifi. It seems like the interface name is appended after the ipv6 
> nameserver. DNS lookups have been failing
> 
> nameserver fe80::a62b:b0ff:fea5:6f5c%wlp3s0

This line is actually valid. The nameserver address is a link-local address. For such addresses, the system must know over which interface they should go as they aren't necessarily unique. You could have a wired connection and a wireless link active at the same time and on both networks this link-local address could exist, so the interface name is always appended to indicate over which interface a specific linkk-local address is to be used (even if you only have one interface). See also:
https://en.wikipedia.org/wiki/IPv6_address#Scoped_literal_IPv6_addresses

The address itself seems fine, too, since your latest Router Advertisements come from this address. So, if DNS lookups fail, I would check on the server side if the configuration is actually correct. You could try pinging the server to test IPv6 connectivity in gneral, check if the nameserver is actually listening on that interface on IPv6 as well or if a firewall rule prevents access.

Cheers,

Timo

Follow-Ups:
Re: Invalid resolv.conf configuration is generatedBruce Schultz
References:
Invalid resolv.conf configuration is generatedBruce Schultz
Archive administrator: postmaster@marples.name