← Back to Blog

You've set up a new server, migrated to a new host, or moved to a new platform, and now you need your domain to point to it. This is one of the most common DNS tasks, and also one where a small mistake can take your site offline or cause hours of confusing partial downtime where some visitors see the new server and others see the old one.

The good news is that pointing a domain to a new server is straightforward once you understand what you're actually changing and in what order. The process comes down to updating a DNS record, but the details, which record, what value, how to handle timing, and how to avoid downtime, are what separate a smooth cutover from a stressful one.

This guide walks through exactly how to point your domain to a new server, the right way, with zero downtime.

What You're Actually Changing

When you "point a domain to a new server," you're updating the DNS record that maps your domain name to the server's address. In most cases, this is an A record (for IPv4) or AAAA record (for IPv6) that contains the server's IP address.

If your new server is identified by a hostname rather than an IP (common with some platforms and CDNs), you might use a CNAME record instead, though not at the root domain. We'll cover both cases.

The key point: you're changing where the name resolves. The domain registration, the nameservers, and everything else stay the same. You're just updating the address that your domain's existing DNS points to.

Before You Start: Gather the Details

You need a few pieces of information before making any changes:

  • The new server's IP address (for an A/AAAA record) or its hostname (for a CNAME). Your hosting provider or server dashboard shows this.
  • Access to your DNS provider. This is wherever your DNS is hosted, which may be your registrar or a separate DNS provider. It's where your existing records live.
  • Your current DNS records. Know what you have now so you can compare before and after. Use the DNS lookup tool at dnsassistant.com/tools to see your current A record and its value.
  • Your current TTL. This determines how quickly the change takes effect and is the key to a zero-downtime cutover.

The Zero-Downtime Process

The secret to pointing your domain to a new server without downtime is preparation and timing. Here's the full process.

Step 1: Get the New Server Fully Ready First

Before touching DNS, make sure the new server is completely set up and able to serve your site or application. This means the website files are deployed, the application is running, the database is connected, and, critically, the server is configured to respond for your domain name (the correct virtual host or site configuration).

Test the new server before pointing DNS at it. Most hosting setups let you access the server by its IP address directly, or by a temporary hostname, so you can verify it works before any visitor is routed to it. Never point your domain at a server you haven't confirmed is working.

Step 2: Lower Your TTL in Advance

This is the step that prevents downtime, and it's the one people most often skip.

Your current A record has a TTL that tells resolvers how long to cache it. If that TTL is high (say, 24 hours), then when you change the record, resolvers around the world will keep serving the old IP for up to 24 hours until their cache expires. During that window, some visitors hit the old server and some hit the new one.

To avoid this, lower the TTL on your A record before the migration. Reduce it to 300 seconds (5 minutes) or even lower. Do this at least as far in advance as the current TTL value, so the old high-TTL cached entries have time to expire and pick up the new low TTL. If your current TTL is 24 hours, lower it to 300 seconds at least 24 hours (ideally 48) before you plan to switch. We explain this timing in depth in our TTL best practices guide.

Step 3: Update the A Record to the New IP

Once the new server is ready and the TTL has been lowered and given time to take effect, change the A record's value to the new server's IP address. In your DNS provider's dashboard, find the A record for your domain (often shown as @ for the root domain and a separate record for www), and update the IP.

If you have both a root domain A record and a www record, update both as appropriate. Some setups point www via CNAME to the root, in which case you only change the root A record.

Because you lowered the TTL in advance, the change now propagates within minutes, not hours.

Step 4: Verify the Change

Confirm the domain now resolves to the new server. Use the DNS lookup tool to query your A record and verify it returns the new IP. Check that your site loads correctly from the new server. Because DNS caching exists at multiple layers (browser, OS, resolver), use the lookup tool rather than just your browser for an accurate picture of what's actually resolving.

Step 5: Keep the Old Server Running Temporarily

Don't shut down the old server immediately. Even with a low TTL, some resolvers and cached entries may take a little time to fully transition. Keep the old server running and serving your site for at least 24-48 hours after the change. This ensures that any visitor still hitting the old IP during the transition still gets a working site, not an error.

Step 6: Restore the TTL

Once the migration is confirmed stable and traffic has fully moved to the new server, raise the TTL on your A record back to a normal value (3600 seconds or higher). This reduces unnecessary query load now that you're no longer in a rapid-change window.

Pointing a Subdomain to a Different Server

The same process applies if you're pointing a subdomain (like app.yourcompany.com) to a new server rather than your root domain. You update the A record for that specific subdomain. If the subdomain doesn't exist yet, you create it. We cover subdomain setup in detail in our subdomain guide.

Using a CNAME Instead of an A Record

If your new server or platform gives you a hostname rather than an IP address (common with managed platforms, CDNs, and PaaS providers), you point your domain using a CNAME record instead of an A record.

Important limitation: you cannot use a CNAME at the root domain (the zone apex). So www.yourcompany.com can be a CNAME, but yourcompany.com cannot. For the root domain pointing to a hostname-based service, you'll need your provider's ALIAS/ANAME feature or the static IPs they provide for apex use. We explain this fully in our A record vs CNAME guide.

Don't Forget These Related Records

Pointing your domain to a new server often involves more than just the A record. Depending on your setup, check whether these also need updating:

  • The www record: Make sure both yourcompany.com and www.yourcompany.com point correctly to the new server.
  • MX records: If your email is hosted on the same server you're migrating from, your MX records may need updating too. If email is hosted separately (e.g., Microsoft 365, Google Workspace), leave the MX records alone, changing the web server's A record does not affect email unless they share infrastructure.
  • TLS certificate: The new server needs a valid TLS certificate for your domain, or visitors will get certificate warnings once DNS points to it. Provision the certificate on the new server before or immediately as you cut over.
  • Other A records: Any other subdomains hosted on the old server need to be migrated and repointed too.

Forgetting MX records is a particularly common and painful mistake: someone migrates their web server, updates the A record, and accidentally takes down email because the old setup had email on the same machine. Always check what else depends on the server you're moving away from.

Common Mistakes

Not Lowering the TTL First

The most common cause of migration downtime. Without lowering the TTL in advance, the change can take up to the old TTL duration to fully propagate, during which traffic is split between old and new servers. If you shut down the old server too soon, the visitors still cached to the old IP get errors.

Shutting Down the Old Server Too Soon

Decommissioning the old server before the transition completes causes errors for anyone still being routed there. Keep it running for 24-48 hours after the change.

Forgetting the TLS Certificate

DNS resolves to the new server, but the new server has no certificate for your domain, so visitors get security warnings. Provision the certificate before cutting over.

Pointing at an Unprepared Server

Changing DNS before the new server is actually ready to serve your site means visitors hit a broken or default page. Always verify the new server works (via its IP or a temporary hostname) before pointing DNS at it.

Forgetting Email (MX Records)

Migrating the web server and inadvertently breaking email because MX records or email services were tied to the old server. Check your email setup before migrating.

How DNS Assistant Helps

Pointing your domain to a new server is exactly the kind of change where monitoring provides confidence and catches problems early:

  • Pre-migration baseline: DNS Assistant documents your current DNS configuration, so you know precisely what you have before you change anything.
  • Change verification: After updating your A record, DNS Assistant confirms the new value is resolving correctly, giving you certainty the change took effect.
  • Real-time alerting: If something goes wrong during the migration, a record reverting, an unexpected value, a resolution failure, you're notified immediately via email, Slack, Microsoft Teams, webhooks, or SMS.
  • Full record monitoring: DNS Assistant watches all your records, not just the one you changed, so if the migration inadvertently affected MX, TXT, or other records, you find out right away.

Having monitoring in place before a migration means you have both a baseline to compare against and immediate visibility into any issues the change introduces.

Get Started

Before pointing your domain to a new server, check your current configuration with the DNS lookup tool at dnsassistant.com/tools, and run a Free Domain Risk Report to document your full DNS setup.

For continuous monitoring that gives you confidence before, during, and after a server migration, sign up at dnsassistant.com.

Start Monitoring Your DNS Today

Get real-time alerts, track record changes, and keep your domains secure with DNS Assistant.

Sign Up Free