Popular Keywords

Categories

No Record Found

View All Results

How to Set Up Email and DNS in Plesk

How to Set Up Email and DNS in Plesk with DNS planning, WordPress backup notes, hosting-panel steps, email/SSL checks, and post-change verification.
How to Set Up Email and DNS in Plesk tutorial for domain, DNS, SSL, business email, WordPress, and hosting verification

How to Set Up Email and DNS in Plesk is a practical hosting workflow for Plesk users managing website DNS, mailboxes, SPF, DKIM, DMARC, and customer domains from Plesk Obsidian. It applies whether the site is a basic WordPress brochure site, a local business site, an ecommerce store, a nonprofit site, or a managed hosting customer account.

Domain, DNS, SSL, and business email work should be treated as launch-critical infrastructure. A small DNS mistake can break a website, hide a WordPress site from customers, stop email, block password resets, damage ads, or make a migration look worse than it is.

Before You Start

  • Confirm whether Plesk is authoritative DNS or only hosting the website.
  • Know whether mailboxes live in Plesk, Google Workspace, Microsoft 365, or another service.
  • Review the DNS template before applying changes to multiple customer domains.
  • Back up or export DNS records for customer-facing domains.

Setup Steps

  • Open the domain in Plesk and review DNS settings.
  • Create mailboxes only when Plesk is the intended mail host.
  • Enable or verify DKIM, SPF, and DMARC according to the active mail provider and Plesk guidance.
  • Secure webmail and mail services with valid certificates where supported.
  • Test website, webmail, inbound mail, outbound mail, and WordPress notifications.

Common Risks

  • Plesk DNS templates can affect many future domains if changed carelessly.
  • A domain can be hosted in Plesk while DNS is actually controlled elsewhere.
  • Mail authentication records must match the actual sender, not only the panel defaults.

Backup And Rollback Notes

  • Export or screenshot DNS before making changes.
  • Back up WordPress before changing URLs, SSL, redirects, SMTP settings, cache, CDN, or hosting destination.
  • Keep old DNS, hosting, and mail access available until the new path is verified.
  • Change one risky system at a time when downtime or missed mail would hurt the business.

Verify It Works

Confirm authoritative DNS, mail routing, authentication, webmail SSL, and WordPress notification delivery after changes.

Fix I.T. Phill Recommendation

Keep ownership clear and verification simple. Know who controls the registrar, DNS, hosting, SSL, WordPress, and email before making changes. After the change, test the real customer path: the website loads, HTTPS is clean, forms deliver, email sends and receives, and admin access still works.

Related Fix I.T. Phill Guides

Sources Checked

Email authentication maintenance note

Email DNS changes should be handled like a launch task, not a quick copy-and-paste job. Before changing SPF, DKIM, DMARC, MX, or SMTP settings, record the current DNS values, confirm who sends mail for the domain, and keep a rollback note in case forms, invoices, password resets, or customer replies stop flowing.

Safe verification checklist

  • Confirm there is only one SPF TXT record for the domain.
  • Check that every active sender is included before tightening SPF or DMARC policy.
  • Verify DKIM signing from the actual mail provider, not only that a DNS selector exists.
  • Start DMARC in monitoring mode when you are not sure all senders are aligned.
  • Send test messages to multiple mailbox providers and review headers before declaring the change finished.

Related email and DNS guides

Picture of admin

admin

Leave a Reply

About Us

Fix I.T. Phill is a site dedicated to sharing knowledge freely to the public.  Use our Contact Us Form to submit new requests for tutorials that we will get up and ready for you ASAP!

Recent Posts

Follow Us

Twitch Twitter

Sign up for our Newsletter

Get the latest information on what is going on in the I.T. World.