DNS setup¶

spawnwp uses two hostnames you choose, both pointing at your VPS:

Variable	Example	Serves
`DOMAIN`	`dev.example.com`	WordPress sites (`/` and `/<site>/`)
`COCKPIT_DOMAIN`	`cockpit.example.com`	The cockpit + per-site Adminer/Mailpit

You can pick any names you control. Common patterns:

Sibling subdomains: dev.example.com + cockpit.example.com
Root + subdomain: example.com + cockpit.example.com
Two unrelated names, as long as both resolve to the same VPS.

Both must resolve before you install

During installation, spawnwp obtains a single Let's Encrypt certificate covering both hostnames using HTTP validation on port 80. If either name does not yet point at the VPS, certificate issuance fails. Set up DNS first and let it propagate.

1. Find your VPS public IP¶

curl -4 https://ifconfig.me      # IPv4
curl -6 https://ifconfig.me      # IPv6 (optional)

2. Create the DNS records¶

In your DNS provider, add an A record (IPv4) for each hostname pointing at the VPS IP. If your VPS has IPv6, optionally add AAAA records too.

Type	Name	Value
A	`dev` (for `dev.example.com`)	`<VPS IPv4>`
A	`cockpit` (for `cockpit.example.com`)	`<VPS IPv4>`
AAAA (optional)	`dev`	`<VPS IPv6>`
AAAA (optional)	`cockpit`	`<VPS IPv6>`

Cloudflare users

Set the records to DNS only (grey cloud), not proxied, at least for the initial install so Let's Encrypt HTTP validation reaches your server directly. You can enable the proxy afterwards if you wish.

3. Verify propagation¶

From your laptop (or the VPS):

dig +short dev.example.com
dig +short cockpit.example.com
# Each should print your VPS IP.

or:

getent hosts dev.example.com cockpit.example.com

Propagation is usually quick but can take from a few minutes up to an hour depending on your provider and TTL. Once both names return the VPS IP, continue to Installation.