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.
If you take a closer look at one of the URL’s source code, you will see that it contains the following:
<frameset rows="100%,*" border="0">
<frame src="http://178.62.87.72" frameborder="0" />
<frame frameborder="0" noresize />
</frameset>
This is because you have set up your domains to “forward” to your IP address. GoDaddy does that by hosting a page for you that loads http://178.62.87.72/. So, even if you browse to http://matrixandcompany.com, nginx will receive a request for 178.62.87.72 because of GoDaddy’s forwarding.
You need to point the DNS records to your droplet instead of setting up forwarding. You can do that by either using GoDaddy’s DNS Manager, or setting your domains’ nameservers to DigitalOcean’s.
The following tutorials should help you point your domains’ nameservers to DigitalOcean’s nameservers and configure the proper DNS records: