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.
This question was answered by @olavamjelde:
Hi, DNS changes can take many hours before it’s updated. So if you think you set it up right, you have to wait and see.
For my set up I have just set up A-name records that point to my floating ip. The floating IP points to the VPS. You dont have to have a floating ip, but it makes it possible to switch servers in the future without waiting for DNS-changes. Also you can make failover clusters etc.
inside nginx I have a server block that listens for both www.domain.tld and domain.tld Then I have another server block for redirect (https).
In theory I could have one block for www with redirect and one for just domain.tld. There are many options, but you have a simple thing that ties it together:
- DNS point A-name to the IP that works for your server.
- Server has to listen for domains