Since this is link-specific DNS, isn't the scope ID implied?
I do see the odd formatting issue in the 'DNS Servers' list:
$ resolvectl status wlp0s20f3
Link 4 (wlp0s20f3)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fe80::dea6:32ff:febe:f88d
DNS Servers: fe80::dea6:32ff:febe:f88d%21943
DNS Domain: lan
but that should be harmless, and is fixed upstream by [1] (though it is
not yet in any of Ubuntu's systemd releases).
I am currently running Kinetic, and with this setting my DNS seems to be
working correctly. What release of Ubuntu are you on?
[1] https://github.com/systemd/systemd/commit/a5e6c8498ca
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2003778
Title:
systemd-resolved uses malformed link-local IPv6 forwarder
Status in systemd package in Ubuntu:
Incomplete
Bug description:
In a network with a local nameserver that has IPv4-address 10.1.0.1
and link-local IPv6-address fe80::2a0:57ff:fe24:b041%2 'resolvectl'
returns:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
Link 2 (ens33)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: fe80::2a0:57ff:fe24:b041
DNS Servers: 10.1.0.1 fe80::2a0:57ff:fe24:b041%21905
DNS Domain: < edited >
Name resolution fails because the indicated 'Current DNS Server'
IPv6-address is an incomplete link-local address. Also the link-local
IPv6-address indicated in the second position of the 'DNS Servers'
line is malformed. Issuing consecutive 'resolvectl' calls have the
last 4 digits in this line changing, i.e. they all show
'fe80::2a0:57ff:fe24:b041%2', which would be the correct link-local
IPv6-address including the interface specification, but then 4 digits
that are not constant.
Workaround:
Take systemd-resoved out of stub-mode with:
(cd /etc && sudo rm -f resolv.conf && sudo ln -s
/run/systemd/resolve/resolv.conf resolv.conf)
The auto generate file '/run/systemd/resolve/resolv.conf' has the
proper specification of the name servers link-local IPv6-address:
nameserver 10.1.0.1
nameserver fe80::2a0:57ff:fe24:b041%2
search < edited >
The broken stub mode is configured with:
(cd /etc && rm -f resolv.conf && ln -s /run/systemd/resolve/stub-
resolv.conf resolv.conf)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003778/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
