A nameserver is the set of servers that tells the internet where to find your domain’s DNS records (the instructions that route visitors to your website and route email to your mailbox).
In plain terms, your domain registrar (where you bought the domain) points your domain to a DNS provider using nameservers, and that DNS provider holds the actual records like A, CNAME, MX, and TXT. When we manage a site on managed WordPress hosting, we often keep DNS with the registrar or move it to a dedicated DNS platform, which is why WordPress hosting and maintenance sometimes includes a DNS cleanup as part of launch.
You update nameservers only when you want to switch who manages DNS for the whole domain. If you are just pointing your domain to a new website, setting up a subdomain, verifying Google services, or fixing email, you usually do not touch nameservers, you edit DNS records where they already live.
| What you’re trying to do | Do you change nameservers? | What you change instead |
|---|---|---|
| Move DNS management to a new provider (example: Cloudflare or a new host’s DNS) | Yes | Nameservers at the registrar |
| Switch web hosting but keep DNS where it is | No | A record or CNAME to the new server |
| Launch a new site and keep email working | Usually no | A/CNAME for the site, keep existing MX and email TXT records |
| Set up email (Google Workspace, Microsoft 365, etc.) | No | MX plus SPF/DKIM/DMARC TXT records |
| Add domain verification for Google tools or SSL/CDN validation | No | TXT record (sometimes CNAME) |
The biggest risk with a nameserver change is downtime because the new DNS provider starts with a blank zone. If the new zone does not include your existing web and email records, your site can stop loading and your email can stop delivering. Before we change anything, we copy the current DNS zone (A, CNAME, MX, TXT, and any custom records), then we confirm the new DNS provider has the same records before flipping nameservers.
Timing-wise, a nameserver update can take anywhere from minutes to 24 to 48 hours to fully spread, depending on caching and TTL settings. For Orlando businesses that rely on calls, form leads, or appointment bookings, we typically schedule nameserver changes earlier in the week and outside your busiest hours, then we verify website, forms, and email deliverability end to end. If you’re also thinking about SSL and trust signals during a move, our FAQ on whether HTTPS affects SEO covers what to watch for after DNS changes.
If you tell us where your domain is registered and where DNS is currently managed, we can quickly confirm whether you need a nameserver change or a simple record update, and we’ll map the safest path so your website and email keep working during the switch.
