I've tested systemd 247.3-3ubuntu3.6 from hirsute-proposed in a VM and
can verify it is working as expected.
I used the configuration provided and kept the VM running for several days
without any crash:
```
root@hh-vm:~# cat /etc/systemd/resolved.conf
[Resolve]
DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com
9.9.9.9#dns.quad9.net
DNSSEC=yes
DNSOverTLS=true
MulticastDNS=no
LLMNR=no
Cache=no
DNSStubListener=yes
Domains=~.
root@hh-vm:~# dmesg | grep segfault
root@hh-vm:~# dmesg | grep "systemd-resolve"
root@hh-vm:~# resolvectl query google.com
google.com: 142.250.185.238 -- link: enp5s0
2a00:1450:4001:813::200e -- link: enp5s0
-- Information acquired via protocol DNS in 121.0ms.
-- Data is authenticated: no
```
DNS requests are working as expected and I could not provoke a crash by
disconnecting the network interface midway through a DNS request,
forcing a timeout.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
