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
- How to Install WordPress: Complete Methods Guide
- How to Back Up WordPress: Complete Methods Guide
- How to Restore WordPress: Complete Recovery Methods Guide
- How to Migrate WordPress: Complete Hosting Move Guide
- How to Maintain a WordPress Website: Complete Business Checklist
- How to Speed Up WordPress: Complete Performance Optimization Guide
- How to Improve WordPress SEO: Complete Search Visibility Guide
- How to Add Business Features to WordPress: Complete Plugin Setup Guide
- Help4 Network hosting and website support
