DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

DNS and cloud init; where is the proper location to set the resolver

I’m running Centos 7. All the usual places to change the DNS resolver have a warning message that this file is created by cloudinit. So where do I actually set the resolver address? That is I need a file not created by cloudinit or any other automatic process.

The only reason I ask is in the last few days my reverse DNS check in Postfix has failed on some IP addresses that are fine, i.e. do have a reverse pointer. For example google gmail servers and comcast.

Show comments
Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sign up now

bunji cord • August 27, 2020

My DO server Ubuntu 20 droplet install did not have resolvconf installed by default. So …

This link has a straight, DO specific answer, and it solved the same issue for me:

https://www.digitalocean.com/community/questions/how-to-permanently-change-dns-nameservers-in-ubuntu-18-04-3-wiki-article-is-not-working

KFSys • February 16, 2020

Hi @gc948486cbc56b8,

If you wish to change your Resolv.conf you’ll need to edit your /etc/NetworkManager/NetworkManager.conf file. Open the file and search for the [main] section in this file. As soon as you find it, Add dns=none just after the [main] tag:

[main]
dns=none

Now that you are done with that part, update your /etc/resolv.conf to whatever you like and restart your NetworkManager.

sudo systemctl restart NetworkManager.service

And that’s it, your resolv.conf should now be safe.

Regards, KDSys

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up