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.

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!
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.
Hello @pjha , I also have the same problem with my droplet. I have followed all the steps that @romeobraindead and @thepouringarts did.
Can you suggest, how to make it permanent. I need that it work please.
Hey there!
The resolvers are having issues. The resolvers are specified in the /etc/resolv.conf file and are set based on the network configuration scripts on the Droplet. You can try rebooting the Droplet once and if the issue still persists, you can try to manually specifying nameserver IP entries in the /etc/resolv.conf file to any of the following for testing. the format looks like this:
nameserver IP.AD.DR.ESS
Google public name servers: nameserver 8.8.8.8 nameserver 8.8.4.4
OpenDNS nameserver 208.67.222.222 nameserver 208.67.220.220
Let me know how it goes.
Regards, Prakash Jha Developer Support