How to Set Up Email, DNS, and SSL on New Hosting
Start with the three records that matter
A new site is not ready until email, DNS, and SSL on new hosting all work together. If one piece is off, you usually see the same symptoms: mail goes to spam, the browser shows a certificate warning, or the domain still points to the old server after a migration.
If you want a cleaner launch path, Hostperl’s shared hosting and Hostperl VPS plans are built for the kind of admin most people actually do: add a site, issue a certificate, check mail flow, and hand the account to a client without dragging support into every step.
Use this tutorial as a launch checklist. It works for shared hosting users, agencies managing client sites, and VPS customers who want a predictable setup before the site goes live.
Check the domain before you touch the site
Before you install WordPress, move files, or update nameservers, confirm who controls the DNS zone. Many problems look like application bugs but are really DNS delays or missing records.
- Open the domain in your registrar panel.
- Confirm the nameservers match your host or DNS provider.
- Check whether the A record, MX record, and TXT records already exist.
- Lower the TTL to 300 seconds a few hours before a migration if you can.
If you are moving a site, compare the current DNS zone with the new one line by line. For a step-by-step migration check, Hostperl’s hosting migration without downtime guide is a useful companion.
Set up email first, not last
Email causes a lot of launch-day tickets, so handle it before you send the announcement. A domain can load perfectly and still fail the business if contact forms, password resets, or invoice notices never arrive.
For a new site, create the mailbox you will actually use: info@yourdomain.com, billing@yourdomain.com, or support@yourdomain.com. Then verify the outgoing settings in your control panel. In cPanel, that usually means checking Email Accounts, Email Deliverability, and Track Delivery. In Plesk or DirectAdmin, look for the mail service, SPF/DKIM tools, and mailbox limits.
Hostperl has a more detailed walkthrough for fresh domains in the new-site SSL, DNS, and email setup tutorial. If you are deciding whether a small business should stay on shared hosting or move to VPS for mail control, the tradeoffs are explained clearly in Shared Hosting vs VPS for Email: What Actually Changes.
Minimum email checks before launch
- SPF includes your host’s mail servers.
- DKIM is enabled and passing.
- DMARC exists, even if it starts in monitoring mode.
- The mailbox can send and receive from webmail.
- The website contact form sends to an external inbox, not the same account you are testing.
A quick test is to send one message to Gmail and one to Outlook, then check the headers. If both land in spam or get delayed, fix the authentication records before you ask anyone to use the address.
Issue the SSL certificate and force HTTPS
Once DNS is close to final, generate the SSL certificate. On most hosting platforms, that means a free Let’s Encrypt certificate, but the workflow differs slightly between shared hosting and VPS.
In cPanel, use SSL/TLS Status or the auto-SSL feature. In Plesk, open Websites & Domains and assign the certificate to the domain and webmail service. On a VPS, you may handle this through the panel or directly in your web server configuration, but the result should be the same: the domain loads over HTTPS without browser warnings.
After issuance, check three URLs:
https://yourdomain.comhttps://www.yourdomain.comhttps://mail.yourdomain.comor your webmail address
If one works and another fails, the certificate may be installed correctly but not bound to every service. That is one of the most common launch-day gaps we see during migrations.
For a cleaner compare-and-choose view of the control panels themselves, Hostperl’s cPanel vs Plesk for hosting customers guide helps if you are deciding where the certificate and mail tools will be easiest to manage long term.
Confirm the DNS records that control mail and web
At this point, the zone should stay simple and easy to read. Extra stale records are a common reason a new site behaves differently for different visitors.
A @ 203.0.113.10
A www 203.0.113.10
MX @ mail.yourdomain.com
A mail 203.0.113.10
TXT @ v=spf1 a mx include:yourhost.example ~all
TXT default._domainkey [DKIM value from panel]
TXT _dmarc v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comIf you host email elsewhere, do not point the MX record at your web server. That mistake is easy to make during a hurried handover and can break delivery for hours.
When you need a broader launch checklist that combines these pieces, use Hostperl’s SSL, DNS, and email setup checklist for new hosting sites. It is especially useful when you are transferring multiple client domains and need a repeatable order of operations.
Move the website files without breaking the live address
If you are launching from a migration, upload the site first, then switch the DNS. That keeps downtime small and makes troubleshooting easier. People often reverse that order, change the nameservers too early, and then spend time chasing a mix of old and new settings.
For cPanel users, the usual path is to restore the account or migrate files into the correct document root, then confirm permissions and database credentials. For VPS customers, check the web root, PHP version, and database host separately before you expose the new server publicly.
- Confirm the website opens on the temporary URL or hosts file entry.
- Check image paths and file permissions after upload.
- Test the homepage, contact form, login page, and checkout or enquiry flow.
- Only then update the final DNS records.
If you are unsure whether your current hosting plan is the right fit for a move, Hostperl’s shared hosting to VPS upgrade signs article covers the practical triggers: mailbox limits, more consistent performance, and more control over DNS and PHP settings.
Fix the common launch problems before customers see them
Most launch issues fall into a small set of patterns. The good news is that they are usually quick to verify.
1) Certificate warning on one hostname
Check whether www, the bare domain, and webmail all point to the same certificate. If one hostname is missing, reissue the certificate with every name included.
2) Mail sends, but replies never arrive
Look at the MX record first. Then check whether the mailbox quota is full, because a full mailbox can look like a routing problem from the outside.
3) The site loads at the old host for some visitors
That usually means DNS is still cached somewhere. Wait for the TTL window to pass, and test from another network before assuming the move failed.
4) Contact forms work in admin but not on the live site
Review SMTP credentials, sender address alignment, and spam filtering. If your form plugin sends using the wrong From address, many providers will reject it even when the site looks fine locally.
For a deeper restore-and-proof approach, the Hostperl guide VPS Backup Testing: How to Trust Your Restore Plan is worth reading after launch. It teaches the same discipline you need for migrations: test the recovery path, not just the happy path.
Use the control panel tools before editing server files
On shared hosting, the panel is usually the safest place to start. That is where you can change email routing, issue SSL, adjust PHP version, and inspect DNS without touching system-wide settings.
On a VPS, you should still use the panel where possible. The more you can confirm in cPanel, Plesk, or DirectAdmin, the less time you spend debugging the wrong layer. Only drop into server-level configuration when you know the panel setting is not enough.
Hostperl’s new hosting site setup guide for cPanel or Plesk is a practical companion if you are starting from a clean account. If the site is already live and you need to move it again later, keep How to Move a Hosting Site Between Panels in 2026 close by.
Final pre-launch checklist
Before you tell anyone the site is ready, run through this short list.
- The domain resolves to the new server from more than one network.
- HTTPS works on the bare domain and
www. - SPF, DKIM, and DMARC records are in place.
- Webmail and SMTP send test messages successfully.
- The homepage, forms, and login pages return the expected content.
- Backups are enabled, and you know how long a restore takes.
If you are moving a business site or client account, do not skip the restore check. A backup that has never been tested is only a copy of a problem.
If you want this setup handled on a host that treats email, DNS, and migration support as part of the service, Hostperl is a solid fit. Our shared hosting plans suit smaller sites, while Hostperl VPS gives you more control when you need cleaner mail routing, panel access, and room to grow.
For launches that need a steadier hand, our team can help you verify the records, issue SSL, and check the migration before you switch live.
FAQ
How long should I wait after changing DNS?
Most changes settle within a few hours if your TTL is low, but some networks cache longer. Test from mobile data and a separate DNS resolver before you assume there is a server problem.
Do I need a VPS for better email?
Not always. Shared hosting can handle normal business email well if SPF, DKIM, and DMARC are configured properly. Move to VPS when you need more control, custom routing, or heavier mailbox use.
Should SSL be enabled before I point DNS to the new host?
Yes, if possible. Issuing the certificate early reduces the chance of users seeing warnings during the first visit after launch.
What is the fastest way to check if mail is broken?
Send a test message from webmail to Gmail and Outlook, then inspect the delivery headers. If the message never arrives, check MX, SPF, and mailbox quota first.
Can Hostperl help with panel migrations?
Yes. If you are moving between panels or replacing an old host, start with the migration checklist and then verify DNS, SSL, and email after the transfer.
