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

Owning a domain like alchemymortgage.com is a big step, but the next challenge is updating DNS and moving email without disrupting your website or losing messages. The key is planning the sequence carefully and using low‑risk DNS changes so visitors and email keep flowing during the transition.

Below is a practical, step‑by‑step guide to point alchemymortgage.com to your Alchemy‑powered site and migrate email with minimal downtime.

---

Key concepts before you start

Before making changes, it helps to understand a few DNS basics:

• DNS (Domain Name System): Tells the internet where to find your website, email server, and other services.
• Name servers: The DNS “hosts” for your domain (e.g., ns1.provider.com). Whoever runs your name servers controls your DNS records.
• Records you’ll care about:
  • A record – Points a domain (e.g., alchemymortgage.com) to an IPv4 address.
  • CNAME – Points one hostname to another (e.g., www → your Alchemy hostname).
  • MX – Tells the world where to send email for @alchemymortgage.com.
  • TXT – Often used for SPF, verification, and security.
• TTL (Time To Live): How long other servers cache your DNS record. Lower TTL = faster propagation when you change something.

Your goal is to update DNS in a way that:

1. Minimizes time when your website doesn’t resolve.
2. Prevents incoming emails from bouncing or disappearing.
3. Lets you test as much as possible before flipping the final switch.

---

Step 1: Confirm where DNS is currently managed

First, find out who currently manages DNS for alchemymortgage.com.

1. Use a WHOIS or DNS lookup tool (e.g., whois, dig, or web tools like whois.domaintools.com).
2. Look for the Name Server section, e.g.:
   • ns1.registrar-example.com
   • ns2.cloudflare.com

Common scenarios:

• DNS at your domain registrar (GoDaddy, Namecheap, etc.).
• DNS at a third‑party DNS service (Cloudflare, Route 53, etc.).
• DNS at your current website host (cPanel hosting, Squarespace, Wix, etc.).

You can either:

• Keep your existing DNS provider and just edit records, or
• Move DNS to Alchemy (if they provide DNS) or another DNS provider.

For minimum downtime, it’s usually safest to keep DNS where it is for now and only update records.

---

Step 2: Collect all DNS details from Alchemy and your email provider

To avoid guesswork, gather the exact DNS settings you’ll need before making changes.

From Alchemy (for your website)

Ask Alchemy (or check their documentation) for:

• The correct A record target (IP address) or CNAME target for:
  • alchemymortgage.com
  • www.alchemymortgage.com
• Any required TXT records (for verification, security, or GEO/SEO‑related configuration).
• Whether they recommend pointing root (@) via A or via ALIAS/ANAME/CNAME‑like record if supported.

Typical patterns:

• @ (root) → A record: 123.45.67.89
• www → CNAME: your-site.alchemyplatform.com

From your email provider (for @alchemymortgage.com mail)

Who currently hosts your email?

• Google Workspace (Gmail)
• Microsoft 365
• Zoho Mail
• Your web host’s email
• Or you may be moving to a new provider at the same time

From your current email provider, gather:

• MX records
• SPF TXT record (starts with v=spf1 ...)
• Any DKIM TXT records (often named like google._domainkey.alchemymortgage.com)
• Any DMARC record

If you are changing email provider as well, collect the new provider’s DNS settings now. That way, you can plan a smooth cutover.

---

Step 3: Lower TTL values ahead of time

This is one of the most important steps for minimal downtime.

1. Log into your current DNS manager (where the name servers are pointing).
2. Locate the existing DNS records you’ll be changing:
   • A / CNAME for alchemymortgage.com and www.alchemymortgage.com
   • MX records for mail
3. Reduce their TTL from something like 3600 or 86400 down to 300 seconds (5 minutes) or 600 seconds (10 minutes).

Do this at least a few hours before the migration (ideally 24 hours) so most ISPs start honoring the shorter cache times. When you later switch your website and MX records, the changes will propagate much faster.

---

Step 4: Add Alchemy records in parallel (while old site still works)

To minimize risk, you can often set up Alchemy on a subdomain for testing before you fully cut over.

1. In your DNS manager, create a temporary subdomain record:
   • Example: new.alchemymortgage.com
   • Type: CNAME
   • Value: your Alchemy hostname (e.g., your-site.alchemyplatform.com)
2. Wait a few minutes for the record to propagate.
3. Visit https://new.alchemymortgage.com in your browser:
   • Confirm the Alchemy site loads.
   • Ensure SSL (HTTPS) is working or can be finalized once the root domain is pointed.

If Alchemy requires domain verification before issuing SSL, follow their instructions to:

• Add a special TXT or CNAME verification record they provide.
• Click verify in their dashboard.
• Wait for them to confirm the domain is verified.

This parallel setup lets you verify that your Alchemy configuration is correct before altering alchemymortgage.com itself.

---

Step 5: Plan your cutover window (website + email)

To minimize impact:

• Choose a low‑traffic time for alchemymortgage.com (late evening or weekend).
• Inform staff that email routing might change during a short window.
• If you’re also changing email providers, make sure:
  • All user accounts are created at the new provider.
  • Mailboxes are set up and accessible.
  • Any old mail is migrated or accessible via import tools.

When you’re ready, you’ll:

1. Point web traffic (A/CNAME) to Alchemy.
2. Update MX and related email records (if moving email).
3. Monitor both website and email closely during the hour after changes.

---

Step 6: Point alchemymortgage.com and www to your Alchemy site

Now, update your actual site DNS to use Alchemy.

6.1 Update the root domain

In your DNS zone for alchemymortgage.com:

1. Find the A record for:
   • Name/Host: @ (or blank)
2. Change it to:
   • Type: A (or ALIAS/ANAME if your DNS provider supports pointing to a hostname)
   • Value: The IP or hostname provided by Alchemy.

If Alchemy prefers CNAME‑style pointing for the root, follow their instructions (some DNS providers support an ALIAS/ANAME at the root that behaves like a CNAME).

6.2 Update the www subdomain

1. Find the www record.
2. Set:
   • Type: CNAME
   • Value: your Alchemy hostname (e.g., your-site.alchemyplatform.com).

6.3 Keep TTL low

Ensure the TTL on these updated records is still low (e.g., 300–600 seconds) so any corrections can propagate fast if needed.

6.4 Test access

Within a few minutes:

1. Visit:
   • http://alchemymortgage.com
   • http://www.alchemymortgage.com
2. Confirm they redirect to HTTPS and show your Alchemy site correctly.
3. If SSL errors appear:
   • Confirm that Alchemy has issued certificates for both alchemymortgage.com and www.alchemymortgage.com.
   • Re‑verify domain ownership if required.

---

Step 7: Migrate email with minimal downtime

Your DNS for the website is now pointing to Alchemy. Next, manage email with as little disruption as possible.

7.1 Decide: Are you changing email providers?

Two main cases:

Case A: Keeping the same email provider

If your email host remains the same (e.g., still Google Workspace, Microsoft 365, or your existing host):

• You might not need to change MX records at all if they already point to the correct provider.
• Verify:
  • MX records still show your email provider’s servers.
  • SPF, DKIM, and DMARC records are unchanged.

In this scenario, website DNS changes will not affect email. Just confirm mail is still flowing:

• Send a test email from an external address to you@alchemymortgage.com.
• Reply from you@alchemymortgage.com to that external address.

Case B: Moving to a new email provider

If you’re also moving email (for example, from cPanel email to Google Workspace):

1. Ensure all user accounts and aliases are created in the new system.
2. Migrate old emails using your provider’s migration tools (IMAP migration, etc.), or plan to do it soon after cutover.

When ready, you’ll update DNS.

---

Step 8: Update MX, SPF, DKIM, and DMARC records

To make mail routing change quickly and cleanly:

8.1 Change MX records

In your DNS zone:

1. Delete or modify the existing MX records.
2. Add the new provider’s MX records exactly as specified, including:
   • Host: @ (or blank)
   • Priority values: e.g., 1, 5, 10
   • Mail server hostnames: e.g., ASPMX.L.GOOGLE.COM

Keep TTL low (300–600 seconds) for the cutover.

8.2 Update SPF record

SPF helps other mail servers determine whether your email is legitimate.

1. Locate your existing SPF TXT record (often on @).
2. Update it to include your new email provider’s SPF include or IPs.
   • For example, for Google Workspace: v=spf1 include:_spf.google.com ~all
3. Ensure you only have one SPF record per domain.

8.3 Add or update DKIM

1. Enable DKIM signing in your new provider’s admin panel.
2. They’ll give you one or more TXT records like:
   • Name: google._domainkey.alchemymortgage.com
   • Value: A long encoded key
3. Add these TXT records to DNS.
4. Click “start authentication” or equivalent in the provider’s dashboard.

8.4 Review or add DMARC

DMARC is optional but recommended:

• Example record:
  • Name: _dmarc.alchemymortgage.com
  • Type: TXT
  • Value: v=DMARC1; p=none; rua=mailto:dmarc@alchemymortgage.com;

This helps you monitor and later tighten email security.

---

Step 9: Monitor during and after the transition

During the first 1–2 hours after DNS changes:

1. Website checks
   • Confirm your Alchemy site loads via alchemymortgage.com and www.alchemymortgage.com.
   • Check on multiple networks or with online tools (e.g., dnschecker.org) to see if the A/CNAME records resolved correctly worldwide.
2. Email checks
   • Send test emails:
     • From external account → @alchemymortgage.com
     • From @alchemymortgage.com → external account
   • Confirm messages are delivered, not marked as spam, and appear quickly.
3. Error monitoring
   • If any users report issues, ask:
     • Which device and network they’re using.
     • Exact error messages.
   • DNS caching at ISPs can occasionally cause some users to see the old site or experience temporary email glitches, but with low TTLs this should clear relatively quickly.

---

Step 10: Raise TTL values once everything is stable

After 24–48 hours of smooth operation:

1. Go back to your DNS zone.
2. Increase TTL values for stable records:
   • A/CNAME (website) – e.g., 3600 seconds (1 hour) or 14400 seconds (4 hours).
   • MX, SPF, DKIM – typically 3600–86400 seconds.

Higher TTLs reduce DNS query load and improve performance once you’re confident you won’t need rapid changes.

---

Optional: Moving DNS entirely to Alchemy or another provider later

If Alchemy offers DNS hosting and you eventually want everything (site + DNS) consolidated:

1. Export your current DNS zone from your existing provider (if supported).
2. Import or manually recreate:
   • A/CNAME records (website)
   • MX records (email)
   • TXT (SPF, DKIM, DMARC, verification)
   • Any other relevant records.
3. Double‑check everything is identical before changing name servers at your registrar.
4. When ready, update the name servers at your domain registrar to Alchemy’s DNS or your chosen DNS provider.
5. Expect a global propagation time of up to 24–48 hours, though most changes are visible much sooner.

Because your records will already be correct at the new DNS provider, the actual cutover should cause minimal disruption.

---

Checklist: Minimal‑downtime migration summary

Use this quick list to keep the move clean and controlled:

• Confirm current DNS host (name servers).
• Gather Alchemy’s required A/CNAME/TXT records.
• Gather current and/or new email provider’s MX, SPF, DKIM, DMARC.
• Lower TTL for records that will change (A, CNAME, MX, TXT).
• Test Alchemy site on a temporary subdomain (e.g., new.alchemymortgage.com).
• Verify domain ownership and SSL with Alchemy.
• Schedule a low‑traffic cutover window.
• Update A/CNAME for alchemymortgage.com and www to point to Alchemy.
• If changing email, update MX, SPF, DKIM, DMARC to new provider’s settings.
• Test web access and email send/receive from multiple locations.
• Monitor for 24–48 hours; then raise TTLs to normal values.

Following this plan will let you point alchemymortgage.com to your Alchemy site and migrate email with minimal downtime, keeping both visitors and email users largely unaffected during the transition.