Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’m having issues with DNS on my Droplet. It cannot connect to outside servers, even ping doesn’t work. Not even dnf update.
So I followed an earlier suggestion found in this forum to persist the resolv.conf file.
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4
/etc/NetworkManager/NetworkManager.conf[main]
plugins = ifcfg-rh,
dns=none
sudo systemctl restart NetworkManager.service
I tried ping after this. No go. Still not working.
So I rebooted this droplet.
Still the same, ping not working. AND the /etc/resolv.conf file got changed to the default again:
nameserver 127.0.0.53
options edns0 trust-ad
What can I do? Is this related to cloud.init? Something unique in Fedora? Never happened to me in CentOS. RedHat suggests to make resolv.conf a symlink instead, is that something we need to do in Fedora??
adf990733ce34c20a86418222e2dda
rajud yadav
50ff4e4b3c6c4999a12403b1ecda95
Erina Jones
05c643336f3a4578a0b414e11ed8fc
378226414b344d3d9ef057316f83e8
792d8c6065294b4da466a26b2a99e4
KFSys
fe9c7f1f3d29491e8c9905409bd159
LittleSeaGreenMorel
504ba8e5f370441283486b46f86d4e
Wilson Karl