How do I point my domain at my own server?

Create an A record for your domain pointing at your server's public IPv4 address, and usually a record for www too (either another A record or a CNAME to the root). If your server has an IPv6 address, add an AAAA record. Then wait for DNS to propagate and confirm with dig. That's the whole job - your domain now resolves to a box you control, with no platform in between.

A record or CNAME for www?

Either works. A CNAME for www pointing at your root domain means you only update the IP in one place (the root A record) if the server ever moves - simpler to maintain. A second A record for www is equally valid and slightly more direct. The generator lets you pick; both are correct.

What TTL should I use?

Lower the TTL (to 300 seconds) a day before you plan to move or cut over, so changes take effect quickly. Once everything is stable, raise it back to an hour or more to reduce DNS lookups. The generator suggests a low TTL while you're setting up; bump it up after.

Free tool · Runs in your browser

Point your domain at your box.

The last step of going self-hosted: make your domain resolve to a server you own. Enter your domain and IP and get the exact DNS records to create — A, www, IPv6, and an SPF record to stop spoofing — plus how to verify it.

Domain

Server IPv4

Server IPv6 (optional)

www handling

Add CAA (only Let’s Encrypt may issue certs) Add SPF (block spoofed email from your domain)

Create these DNS records

Type	Name	Value	TTL

Verify after propagation

Propagation takes minutes to a few hours. Lower TTL to 300 before a planned move; raise it back once stable.

The piece with no platform in it

Pointing a domain at your own server is the moment self-hosting becomes real: a few DNS records and your domain resolves to hardware you control, with no platform sitting in the middle taking a cut or holding the keys. It's also genuinely simple — an A record and you're most of the way there — which is worth remembering when a platform makes “just use our domain” sound like the only option.

DNS is one more piece of infrastructure to own and keep correct, alongside the server, the certs, and the config. Keeping all of it consistent and verifiable — and knowing the moment something points somewhere it shouldn’t — is the standing job a control plane handles across everything you run.

Related free tools

Deploy to your own serverPush-to-deploy, your box systemd service generatorKeep your app running Reverse proxy + HTTPSCaddy / nginx + HTTPS Backup script generatorDump, offsite, restore

All free tools →

Your domain, your server, your keys.

Infraveil runs your backend on infrastructure you own, end to end — so the domain, the server, the certs, and the config are all things you control and can prove, with no platform in the middle.

See how it works

Get the self-hosting setup playbook

DNS, TLS, proxy, and the steps to stand up a backend you own. No spam.