Point your domain at Serverlys

Step 1: Decide: nameservers or an A record

Changing nameservers hands all DNS for the domain to Serverlys — simplest, and right for most people. Changing only the A record points the website here while leaving everything else, including email, answered where it is now. If your email is with Google Workspace or Microsoft 365 and you do not want to recreate those records, use the A record.

Step 2: Write down what you have now

Before changing anything, screenshot the current DNS records — especially MX, TXT and any CNAME. If you switch nameservers without copying these across, email stops. This is the single most common way a domain move breaks a business.

Step 3: Lower the TTL, then wait

Set the TTL on the record you are about to change to 300 seconds and leave it for at least as long as the old TTL was. Resolvers around the world are caching the old value; this is how you stop them caching it for another day after you make the change.

TTL: 300

Step 4: Make the change

For nameservers, replace the existing entries with the Serverlys pair. For an A record, set the host to @ and the value to your server IP, then add a CNAME for www pointing at your domain.

A     @     your.server.ip.address
CNAME www   yourdomain.com.

Step 5: Confirm it resolves here

Check from a device that has never visited the new server — a phone on mobile data is ideal. Your own machine may have the old answer cached for hours regardless of TTL.

Step 6: Issue the SSL certificate

Only after the domain resolves to us. Certificate issuance validates by looking up the domain, so it cannot succeed before DNS points here. Then raise the TTL back to something sensible, like 3600.