systemd update breaks DNS resolution on Fedora 33 cloud instances
by Tadej Janež
Hi all!
I was recently hit by this and it took me some time to figure out what
was going on.
I provisioned a fresh Fedora 33 cloud instance on DigitalOcean.
After completing the initial upgrade via 'dnf update' and rebooting the
system, DNS resolution stopped working.
I did a little debugging and saw that no DNS servers were configured:
$ resolvectl dns
Global:
Link 2 (eth0):
Link 3 (eth1):
$ resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eth0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Link 3 (eth1)
I was confused how could that happen since running 'dnf update' on the
first boot clearly required DNS resolution to work.
It turns out a recent systemd update, namely systemd-246.7-2.fc33
(https://bodhi.fedoraproject.org/updates/FEDORA-2020-3616681a70),
includes this commit:
https://src.fedoraproject.org/rpms/systemd/c/ed795fb1fc9a2c20ebcac34bdf7e...
which removes the fallback DNS server list (i.e. Cloudflare's and/or
Google's DNS servers) due to concerns over DNS requests being
personally identifying information (PII) in the sense of GDPR?
In combination with NetworkManager's DNS server handling being disabled
via cloud-init:
$ cat /etc/NetworkManager/conf.d/99-cloud-init.conf
# Created by cloud-init on instance boot automatically, do not edit.
#
[main]
dns = none
this results in no DNS servers being configured on the system.
The consequence is that Fedora 33 cloud instances are broken after
updating the systemd package to version 246.7-2.fc33.
(I haven't checked but if Fedora 34 cloud images include this version
of systemd, then DNS resolution won't work even on first boot.)
Please advise on the best steps to fix this issue.
Regards,
Tadej
3 years
Info about documentation
by Peter Boy
Please, could someone direct me to the latest cloud documentation? Using the "search engine I trust", I have found only very old docs (manual for Fedora 25 and https://fedoracloud.readthedocs.io/en/latest/index.html (about 2016) )
I’m currently working on updating and extending the documentation for Fedora Server. I would like to include the use of cloud images on a standalone Fedora server, either via vagrant or using the --cloud-init option in virt-install version 3. The former was described in Fedora Magazine. I have not yet found anything on the latter. Does anyone have any experience with this?
Thanks
Peter
3 years, 3 months
