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.
Hey there 👋
If you’ve kept your domain on Namecheap and added an A record pointing app.mydomain.com to your Droplet’s IP, that’s generally all you need.
First, make sure the A record is actually for app and not something like www.app. Then, check that your web server, whether it’s Nginx or Apache, is properly configured to serve traffic for app.mydomain.com. If the server isn’t set up to recognize the domain, you’ll get a default page or an error.
It’s also worth running a quick DNS lookup with dig app.mydomain.com or using a tool like https://www.digitalocean.com/community/tools/dns to confirm that your record has propagated globally. Keep in mind that DNS changes can sometimes take time, and local DNS caching or browser cache might delay what you see, trying in incognito mode or flushing your DNS cache can help.
Let me know what the exact error is that you are getting.
- Bobby
Heya,
Make sure your DNS has actually propagated:
https://www.digitalocean.com/community/tools/dns
It sounds to me like the A record you have created for your subdomain is not actually working at all.
Heya, @sap
The DNS should have updated for the 24 hours it’s been but you can still check if all locations return the expected IP address:
Regards