Every self-hosting guide assumes your domain already points at the server. Here’s that step, start to finish.
Step 1 — Find your VPS IP
Your provider’s dashboard shows the public IPv4 address, or run on the server:
curl -4 ifconfig.meStep 2 — Create an A record
In your domain registrar’s DNS settings, add:
| Type | Name | Value | TTL |
|---|---|---|---|
| A | @ (root) | your.server.ip | 3600 |
| A | cloud (subdomain) | your.server.ip | 3600 |
@ points the root domain; a name like cloud creates cloud.yourdomain.com. Add one A record per subdomain you’ll use (cloud, photos, vault, n8n…), all pointing at the same IP — the reverse proxy sorts out which app each one reaches.
Step 3 — Wait for propagation
Changes usually take effect within minutes but can take a few hours. Lower the TTL beforehand if you expect to change records often.
Step 4 — Verify
dig +short cloud.yourdomain.com # should print your server IP
# or: ping cloud.yourdomain.comOnce it resolves, you’re ready to add HTTPS with Nginx Proxy Manager and deploy apps like Nextcloud.
Need a VPS first?
If you don’t have a server yet, start here: Best VPS for Self-Hosting. Budget pick Hetzner , managed pick Cloudways , and for cross-border use cases see the VPS for China access guide.
