[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
Right, I understand why it would be needed in a ping. But since the DNS
server config in systemd-resolved applies to a specific link, the scope
ID is implied.
As far as your desktop vs server systems, maybe it's the difference
between the interfaces available on each system? If you only have one
n
I'm on Ubuntu 22.04 LTS. I always need to provide the interface
specification when using link-local IPv6-addresses, e.g. a simple 'ping
fe80::2a0:57ff:fe24' doesn't work but 'ping fe80::2a0:57ff:fe24%2' does
the trick. I couldn't figure out why this is required on my desktop
Ubuntu system. In contr
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:
4 matches
Mail list logo
