#10 Problems with cloud-init DNS settings?
Closed 14 days ago by pboy. Opened 4 months ago by catanzaro.

I noticed when spinning up a F33 droplet on DigitalOcean that the default DNS server is 1.1.1.1 instead of DigitalOcean's DNS servers, as expected. Then after the first dnf update, 1.1.1.1 goes away and no DNS is available at all, because the first update removes fallback DNS servers. Oops?

At first I thought this was a bug on DigitalOcean's end, but I guess it's really probably our fault, since DigitalOcean is just using cloud-init like all major cloud providers, and we never updated cloud-init to understand systemd-resolved. Asking around, I hear that the Server Working Group is nowadays caring for Cloud Edition, so... I guess this is the right place to report the issue? (cloud-init's issue tracker is on Launchpad, so that doesn't seem like a good place.)

For comparison: Ubuntu droplets use DigitalOcean's DNS, and Ubuntu uses systemd-resolved. But for Ubuntu, I think this happens in cloud-init's netplan.py, not so relevant for us.

CC: @zbyszek


Transfered to Cloud WG

Metadata Update from @pboy:
- Issue status updated to: Closed (was: Open)

14 days ago

Transfered to Cloud WG

Where's that?

Transfered to Cloud WG

Where's that?

We discussed on IRC meeting 2021-03-03
see https://meetbot.fedoraproject.org/fedora-meeting/2021-03-03/fedora-server.2021-03-03-18.04.log.html 18:53:40 ff

Best way to proceed might be to join the next Cloud IRC meeting

Tuesday, 2021-04-27 16:00 UTC (or any other Tuesday same time) at fedora-meeting-1@irc.freenode.net

Login to comment on this ticket.

Metadata