DNS A Record Checklist for Pointing Domain to VPS
To make a domain load a website on your VPS, the domain DNS must point to the correct server IP. The most common setup is an A record for the root domain and another record for www if needed.
Common DNS mistakes
- A record points to old hosting.
- www record is missing.
- Cloudflare proxy hides origin issues.
- DNS propagation is misunderstood.
- Root domain and www point to different places.
- Wrong IP copied from VPS provider.
Checklist
- Copy the correct public IPv4 address from your VPS provider.
- Open your DNS manager.
- Create or update the A record for the root domain.
- Create or update www record if needed.
- Remove old conflicting records.
- Set TTL to a reasonable value.
- Wait for DNS propagation.
- Check DNS from multiple locations.
- Confirm Nginx server block matches the domain.
- Install SSL after DNS points correctly.
Final check
DNS is correct when the domain resolves to the VPS IP, Nginx has a matching server block and the website loads through the browser.
Estimated Time
15–30 minutes
Use Case
Use this checklist when connecting a domain name to a VPS for WordPress, Nginx, Docker or AI Automation services.
Common Mistakes
- Editing DNS at the wrong provider.
- Leaving old A records active.
- Forgetting www.
- Installing SSL before DNS resolves.
- Assuming DNS updates are instant.
Related Commands
dig example.com
dig www.example.com
curl -I http://example.com
sudo nginx -t