# Site not loading after a DNS change

Use this checklist when a new domain, VPS, Nginx route, or HTTPS setup does not load after DNS was changed.

## First rule

Separate DNS, HTTP, HTTPS, and server routing. They can fail in different places while the browser shows one vague error.

## Safe command path

1. Check the domain record:

```sh
dig +short example.com A
```

2. Check plain HTTP:

```sh
curl -I http://example.com
```

3. Check HTTPS:

```sh
curl -I https://example.com
```

4. Check Nginx config on the server:

```sh
sudo nginx -t
```

5. Check the served document root:

```sh
grep -RInE 'server_name|root|listen' /etc/nginx/sites-enabled /etc/nginx/conf.d 2>/dev/null
```

## What to avoid

- Do not keep changing DNS records before checking what DNS currently returns.
- Do not reload Nginx until `nginx -t` passes.
- Do not request new certificates repeatedly before confirming DNS and HTTP reachability.
- Do not assume HTTPS is broken when HTTP is still pointing at the wrong server.

## Good project note

Record the domain, expected IP, actual DNS answer, HTTP status, HTTPS status, Nginx config test, current release path, and next action.