DNS A Record Checklist for Pointing Domain to VPS

halfbrain_logo512adminJune 12, 2026
169 lượt xem

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

  1. Copy the correct public IPv4 address from your VPS provider.
  2. Open your DNS manager.
  3. Create or update the A record for the root domain.
  4. Create or update www record if needed.
  5. Remove old conflicting records.
  6. Set TTL to a reasonable value.
  7. Wait for DNS propagation.
  8. Check DNS from multiple locations.
  9. Confirm Nginx server block matches the domain.
  10. 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.

Checklist Type VPS Setup
Level Beginner
Risk Level Medium Risk
Estimated Time 15–30 minutes

When to Use This Checklist

Use this checklist when connecting a domain name to a VPS for WordPress, Nginx, Docker or AI Automation services.

Required Tools

Domain registrar access, DNS manager, VPS IP address, Nginx server block, browser, DNS checker

Before You Start

Make sure you are using the public IPv4 address of the correct VPS and not an internal or old IP address.

Structured Checklist Steps

  1. Copy VPS public IP.
  2. Open DNS manager.
  3. Update root A record.
  4. Update www record.
  5. Remove conflicting old records.
  6. Check TTL.
  7. Wait for propagation.
  8. Verify DNS resolution.
  9. Check Nginx server block.
  10. Install SSL after DNS works.
See also  Uptime Monitoring Checklist for Small Websites

Verification Steps

  1. Domain resolves to correct IP.
  2. www behavior is correct.
  3. Website loads from VPS.
  4. SSL can be issued.

Rollback Plan

If DNS points to the wrong server, restore the previous record or update the A record to the correct VPS IP and wait for propagation.

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

Share:

Disclaimer: The guides, checklists, commands, and examples on HalfBrain.net are provided for educational and operational reference only. Server environments, hosting providers, software versions, security settings, and WordPress configurations can vary, so you should always review commands before running them on your own system. We do our best to keep the content accurate and useful, but we cannot guarantee that every command, configuration, or recommendation will fit every environment. Always back up your website, database, and server configuration before making changes. HalfBrain.net is not responsible for data loss, downtime, security incidents, misconfiguration, or other issues that may result from applying the information on this website. Use the material at your own discretion.

halfbrain_logo512
admin

HalfBrain.net is a practical field notebook for people who want to self-operate websites, VPS servers, Linux systems, Docker stacks, Nginx configurations, DNS records, SSL certificates, and AI automation workflows. Our goal is simple: turn messy infrastructure problems into clear, repeatable checklists, commands, and operating procedures. We focus on practical execution, not theory for theory’s sake.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related articles: