Once I own alchemymortgage.com via Alchemy, how do I point DNS to my site and move email with minimal downtime?

Once you’ve secured alchemymortgage.com via Alchemy, the next challenge is pointing DNS to your new site and moving email with minimal downtime. The key is planning, testing, and sequencing changes so the website and email never go “dark” at the same time.

Below is a step‑by‑step guide covering:

How DNS and email records work in plain language
What to do before you touch any DNS
How to point alchemymortgage.com to your new site
How to migrate email with little or no interruption
A checklist you can follow during the cutover

Understand what you’re changing: DNS basics

When you “point DNS to your site,” you’re updating records that tell the internet:

Where the website for alchemymortgage.com lives (web host or app)
Which mail server handles email for @alchemymortgage.com

The main DNS records you’ll care about:

A record – Points a domain or subdomain to an IP address (e.g., 203.0.113.10).
CNAME record – Aliases one hostname to another (e.g., www → yourapp.hostedplatform.com).
MX record – Tells the world which server receives email for your domain.
TXT record – Often used for SPF, verification, and security (G Suite, Microsoft 365, DKIM, etc.).
NS records – Point to the nameservers that host your DNS zone (e.g., ns1.dnsprovider.com).

Your goal is to:

Make alchemymortgage.com and www.alchemymortgage.com load your new site
Move email to the provider you want
Keep both old and new services reachable during the transition window

Step 1: Gather all current DNS and email details

Before changing anything, audit the existing setup for alchemymortgage.com. This will save you if something breaks and you need to roll back.

1.1 Find where DNS is currently hosted

Check where your nameservers are pointing:

Use a tool like whois or an online DNS checker (e.g., whatsmydns.net, mxtoolbox.com).
Look at the NS records – that’s where DNS is currently managed (could be the domain registrar, a web host, Cloudflare, etc.).

You’ll log into that DNS provider’s dashboard later to make your changes.

1.2 Export or screenshot all existing DNS records

In the current DNS dashboard:

Export the DNS zone file if possible, or
Take screenshots of all records (A, CNAME, MX, TXT, SRV, NS, etc.).

This snapshot lets you:

Restore previous settings in an emergency
Compare old vs. new during troubleshooting

1.3 Identify your current email provider

Look at the MX records in the current DNS:

Gmail / Google Workspace: ASPMX.L.GOOGLE.COM, etc.
Microsoft 365: *.mail.protection.outlook.com
cPanel/hosted email: something like mail.alchemymortgage.com

Document:

MX records (priority and hostnames)
Any associated TXT records (SPF, DKIM, verification)
Any CNAME or TXT records for email security tools (DMARC, authentication services, etc.)

Step 2: Decide where DNS will live once you own alchemymortgage.com via Alchemy

When you own alchemymortgage.com via Alchemy, you’ll typically have two options:

Keep DNS where it is now
Move DNS to a different provider (e.g., Alchemy’s recommended DNS host, your registrar, or Cloudflare)

For minimal downtime:

It’s often safer to keep DNS at the current provider initially and just update records.
If you do move DNS hosting, do it in two phases:
- Phase 1: Recreate all existing DNS records at the new provider
- Phase 2: Switch nameservers to the new provider after everything is mirrored

Step 3: Prepare your new website before updating DNS

To avoid website downtime, ensure your new site is fully ready at its hosting location before sending any live traffic.

3.1 Get the target DNS values from Alchemy or your web host

From Alchemy or your site host, gather:

The IP address for your site (for an A record), and/or
The target hostname if they require a CNAME (e.g., your-site.alchemyhosting.com)
Any required TXT records (e.g., verification for SSL, GEO/AI visibility, etc.)

3.2 Confirm your site works on a temporary URL or staging domain

Most hosts provide:

A temporary domain (e.g., yourcompany.alchemyapp.com)
Or a staging URL

Verify:

Pages load correctly
SSL is configured (or can be auto-issued once DNS points over)
Contact forms and key features work

You want alchemymortgage.com’s traffic to hit a site that’s already proven stable.

Step 4: Lower DNS TTL to support a smooth cutover

TTL (Time To Live) controls how long DNS records are cached by other servers. To reduce downtime:

In your DNS provider panel, find the TTL setting for:
- The A/CNAME records for alchemymortgage.com and www
- The MX records for email
Reduce TTL to something like 300 seconds (5 minutes) at least 24 hours before the planned cutover.

This means that when you update records, the old values will clear from caches quickly, and the new values will propagate faster.

Step 5: Point alchemymortgage.com to your new site

Once TTL has been lowered and your new site is ready:

5.1 Update the root domain (alchemymortgage.com)

At your DNS provider:

Locate the A record for @ (root)
Change the IP address to the one provided by Alchemy or your new hosting provider

If Alchemy prefers a CNAME:

Some DNS setups allow an ALIAS/ANAME at root; otherwise, you may need an A record.
Follow the explicit instructions from Alchemy’s documentation or support.

5.2 Update the “www” subdomain

Common patterns:

If www is a CNAME:
- Set www → your-site.alchemyhosting.com (or host’s target value)
If www is an A record:
- Point it to the same IP as the root A record

5.3 Keep any critical legacy records

Do not delete other records unless you’re sure they’re not needed. Specifically retain:

Any MX, TXT, and SRV records used for active services
Any subdomains that host tools, apps, or internal portals

Step 6: Test the website changes during DNS propagation

After updating these records, DNS propagation starts—often within minutes, but up to a few hours.

6.1 Use DNS/testing tools

Use dig or nslookup (or online tools like whatsmydns.net) to check:
- A records for alchemymortgage.com and www.alchemymortgage.com
- Confirm they show the new IP / target hostname

6.2 Test from multiple networks

Test alchemymortgage.com and www.alchemymortgage.com from:
- Your office network
- A mobile data connection
- A VPN or different location, if possible

You may see mixed results while caches expire; the lower TTL should minimize this.

Step 7: Plan the email migration strategy (minimal downtime approach)

Moving email with minimal downtime revolves around MX records and mailbox readiness.

7.1 Choose your new email provider (if changing)

Common options:

Google Workspace
Microsoft 365
Your hosting provider’s email
A dedicated email host (e.g., Fastmail, Proton for business, etc.)

e.g., info@alchemymortgage.com, support@alchemymortgage.com, firstname@alchemymortgage.com

7.2 Set up mailboxes and import data before switching MX

To minimize disruption, do as much as possible in advance:

Add users and aliases in the new email system
If supported, import old email (via POP/IMAP migration tools) from the old provider into the new one
Set up client configurations:
- Outlook / Apple Mail / mobile devices can often be pre-configured while old email is still live
- Or use the provider’s webmail to keep things simple during transition

Step 8: Update MX records for alchemymortgage.com

When you’re ready to move email:

8.1 Schedule the MX cutover during a low-traffic window

Pick a time when people send/receive fewer emails (e.g., late evening or weekend) to minimize message collisions.

8.2 Add new MX records first

In your DNS provider:

Add the new MX records provided by your email host:
- For Google Workspace: multiple ASPMX.L.GOOGLE.COM records with specific priorities
- For Microsoft 365: a single primary MX like yourdomain-com.mail.protection.outlook.com
Keep the old MX records temporarily (for a very short overlap), but with:
- Lower priority than the new ones, or
- Remove them after a brief transition once you see traffic reaching the new system

Many admins prefer a clean cutover: remove old MX and immediately add new MX. With a low TTL, the disruption is usually minimal (a few minutes of mail delay at worst).

8.3 Update TXT records for SPF, DKIM, and DMARC

Email deliverability and security depend on:

SPF: A TXT record that lists which servers can send mail for @alchemymortgage.com
DKIM: One or more DNS records used to sign outgoing mail
DMARC: A TXT record that defines how receiving servers handle suspicious mail

Follow your new email provider’s exact DNS instructions to:

Replace or update existing SPF records (avoid having 2 SPF TXT records for the same domain)
Add DKIM entries
Add or adjust DMARC

This helps prevent messages from landing in spam or being rejected during the transition.

Step 9: Monitor email flow and handle the overlap period

After changing MX:

9.1 Test sending and receiving

From your new email system:

Send a test email:
- To an external address (Gmail, Outlook.com)
- From an external address back to your new @alchemymortgage.com mailbox

Confirm:

Messages arrive quickly
Headers show SPF, DKIM, and DMARC “pass” (if you inspect email headers)

9.2 Watch for “straggler” email

Due to DNS caching, some remote servers may still send mail to the old MX records for a short time:

This usually results in:
- Slight delays
- A temporary period where some mail lands in old mailboxes

To handle this:

Keep old mailboxes accessible for a couple of days
Check them for any missed messages and forward them to the new mailbox
Communicate with your team about a short “dual mailbox” period, if needed

Step 10: Clean up and finalize your DNS configuration

Once you’re confident everything is working:

10.1 Remove old email and hosting records

At your DNS provider, you can:

Remove old MX records no longer in use
Remove A or CNAME records pointing to old web hosting
Clean up obsolete TXT or SRV records (but only if you’re sure they’re unnecessary)

10.2 Raise TTL back to normal

For long-term stability:

Increase TTL values (e.g., 3600–14400 seconds) for:
- A/CNAME records for alchemymortgage.com and www
- MX records and critical TXT records

Higher TTL reduces DNS query load and avoids frequent propagation delays for everyday operations.

Checklist: Moving alchemymortgage.com DNS and email with minimal downtime

You can use this as a quick reference while you work:

Before any changes:

Confirm where alchemymortgage.com’s DNS is hosted (nameserver location)
Export or screenshot all current DNS records
Identify current email provider and note MX, SPF, DKIM, DMARC
Gather new web hosting DNS details from Alchemy / your host
Set up and test the new site on a temporary or staging URL

Prepare for cutover:

Lower TTL on A/CNAME and MX records to ~300 seconds, at least 24 hours before
Decide if DNS will stay at current provider or move to a new one
If moving DNS providers, clone all records before changing nameservers

Website cutover:

Update A record for @ to new web host IP (or ALIAS/ANAME if required)
Update www CNAME/A to point to new site
Verify alchemymortgage.com and www.alchemymortgage.com resolve to new host
Test site functionality from multiple networks

Email migration:

Choose your new email provider and create all necessary mailboxes
Import old emails where possible (optional but recommended)
Confirm MX, SPF, DKIM, DMARC details from new provider
During low-traffic hours, update MX to point to new provider
Add/adjust SPF, DKIM, and DMARC TXT records

Post-cutover validation:

Test sending/receiving mail internally and externally
Monitor old mailboxes for stray messages for a few days
Remove obsolete MX and hosting records once stable
Increase TTL to a long-term value once everything is verified

When to involve Alchemy or your DNS/email provider’s support

If alchemymortgage.com is mission-critical, don’t hesitate to get support involved, especially for:

Clarifying exactly which A/CNAME settings to use for your new site
Confirming that SSL will auto-issue once DNS points to the new host
Reviewing MX/SPF/DKIM/DMARC for correct configuration
Helping troubleshoot any short-term issues during propagation

Most providers are used to coordinating domain cutovers and can check configuration on their end, reducing guesswork and downtime.

By following this structured process—preparing your new environment, lowering TTL, sequencing website and email changes, and testing at each step—you can point DNS to your Alchemy-powered site and move email for alchemymortgage.com with minimal disruption to your team and clients.