I've tested systemd 245.4-4ubuntu3.13 from focal-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@ff-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=opportunistic
MulticastDNS=no
LLMNR=no
Cache=yes
DNSStubListener=yes
Domains=~.
root@ff-vm:~# dmesg | grep segfault
root@ff-vm:~# dmesg | grep "systemd-resolve"
root@ff-vm:~# resolvectl query google.com
google.com: 2a00:1450:4001:809::200e -- link: enp5s0 172.217.18.110 -- link: enp5s0
-- Information acquired via protocol DNS in 177.4ms.
-- 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.
I've tested systemd 245.4-4ubuntu3.13 from focal-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: resolved. conf 182.19. 48#dns2. digitalcourage. de 1.1.1.1# cloudflare- dns.com 9.9.9.9# dns.quad9. net opportunistic 4001:809: :200e -- link: enp5s0
172. 217.18. 110 -- link: enp5s0
```
root@ff-vm:~# cat /etc/systemd/
[Resolve]
DNS=46.
DNSSEC=yes
DNSOverTLS=
MulticastDNS=no
LLMNR=no
Cache=yes
DNSStubListener=yes
Domains=~.
root@ff-vm:~# dmesg | grep segfault
root@ff-vm:~# dmesg | grep "systemd-resolve"
root@ff-vm:~# resolvectl query google.com
google.com: 2a00:1450:
-- Information acquired via protocol DNS in 177.4ms.
-- 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.