Help with Email & Changing Name Servers/Webhost?
Alright, time to ask for help. I designed a website for my cousin using Wordpress, hosted via BlueHost. It's 99% done.
The problem: she'd originally registered her domain through wordpress.com. She also has an email through that, which she accesses via Google Workplace. We've transferred the domain, but the nameservers are still registered to wordpress.com. I've found the guides for transferring nameservers on BlueHost and wordpress.com, but this is a step above what I've dealt with in the past.
My main concern and frustration are the email. She's already using it for work, and I want to make sure there's no downtime, but I... honestly have no idea how it's even set up, right now. Or how this would work when transferring hosts entirely. Attempts to search it haven't been too helpful for me.
So my questions: How will changing nameservers impact the email? Would updating them potentially just... break her email entirely? Need her to set up the email separately? And if she does, can it be kept through Google Workplace/Gmail since that's what she's already using? Is it fine to leave it as-is? I assume not but her wordpress.com account shows that it expires in 2027, so...?
Just, please help.
You should be able to cutover with minimal-to-no downtime (email is generally pretty smart; if the domain is unavailable, remote clients will retry a couple times before giving up). MX records are especially important here as they tell email servers where emails should go (TXT are also important as some of these are used to verify you are who you say you are when sending emails). Assuming you copy everything from the old DNS manager to the new one exactly, there should be no need to reconfigure anything on Google Workspace.
Once you have all the DNS records copied over from Wordpress to BlueHost, updating the nameservers to point at BlueHost should keep everything working consistently. Do double-check your configuration after updating the nameservers (then again after a few hours, it can take time to propagate across the internet).
This tool from Google Admin Toolbox is very useful for checking DNS configurations, it's essentially a web version of the
dig
command-line tool. If you put the domain in there, you should be able to validate that the MX records match what you expect, then check the NS records to make sure they point at BlueHost. If the NS records still point at Wordpress that probably just means it's still propagating and you should check back later.In the future, I'd suggest using a third-party service to manage your domains like Dynadot, Porkbun, or Cloudflare (no special love for any of the three, but I've used them all before. They all offer the same basic set of features). IMO it's just a good way to hedge your bets in case you want to quickly change from a bad webhost.
I don't know about BlueHost specifically, but generally, when transferring a domain name to a different provider, it has the option to keep your existing DNS records. You should make sure that the records are transferred, especially the ones that have the type
MX
orTXT
, as those are usually the ones needed for email to work.If you do that, nothing should break and she would be able to use her email through Google Workspace the same way she does. Domains and DNS are weird though, so while it should be fine, there may be a bit of downtime while the name is being transferred. There isn't anything you can do about that, DNS is a pretty janky system so it can sometimes be unreliable. Though most likely there will be no downtime, and even if it happens, it's going to be a few hours max.
Can you elaborate on what you mean by "transfer the domain"? Do you mean you've initiated a domain transfer from WordPress.com to bluehost?
That step is probably not, strictly speaking, necessary. You can purchase your domain through one entity and have everything else (even the DNS) running through another.
Quick primer:
You DNS provide is the place where a lot of this transition gets handled.
If you don't change DNS providers, you could leave the domain registration and DNS with WordPress come, and just go into WP's DNS configuration tool and point your A record to bluehost to get the domain live for the website hosted at bluehost. In that case, also you shouldn't need to do anything to the email. It will remain pointed at the gmail servers.
If you've already started transferring the domain to bluehost, you will need to use them as your DNS provider (or configure a third party once the transfer is complete). In either case, you should ASAP copy all the DNS MX and TXT records from the old DNS config to the new one.
During the transition from one DNS provider to another, there may be some time when people resolve the old server or the new one. If they are both configured for Google email, everything should go where it is supposed to. If any mail fails to deliver, most mail servers will hold it for a day the retry delivery. So you shouldn't lose much, if anything.
In the future, i would try to get your domains transferred to a reliable registrar and operate them from there. I have been using namecheap for years and been happy with them. Namecheap can also do the DNS, but I use cloudflare for DNS. It's free for the basic stuff, which is all you need. By having those parts separate from the host and email provider, it's easier to make changes to the hosting and email provider as needed.
Aside from
MX
, you'll need to copy theSPF
,DKIM
, andDMARC
records. As long as both nameservers are serving the same content then there will be no downtime when switching to the new nameservers.One thing to note: eg. if you are sending mail from a server like self-hosted wordpress, and you are migrating that to a new server you'll want to switch that over in the
SPF
record. This might show up as anip4:169.254.0.0
or something like that, if169.254.0.0
is the old server IP address then replace that with the new IP address.Are those ever separate record types? I know that there are SPF records, but I've never actually seen them, almost all mail providers just use TXT
Edit: Wikipedia says that SPF records are discontinued due to the lack of support
I wrote records not record types. You still very much need
SPF
information but yes, most DNS information is stored asTXT
record types. I hadn't heard of theSPF
record type before but SPF records are still very important to email systems