Setting Up Business Email on Your Own Domain
Business email on your own domain means your address is you@yourbusiness.com.au and the mailbox sits on the mail servers that come with your hosting, rather than on a free provider's domain or a mailbox you rent per person. Two things have to be right. The mailbox has to exist, and the domain's DNS has to tell the rest of the internet where to deliver.
The second part is where most of the trouble starts, because a missing or wrong record is invisible. The mailbox works, mail sends, and then half the replies land in a spam folder and nobody knows why.
Why the address matters more than it looks
A customer reads your address before they read your message. An address on a free provider looks improvised, and it puts your business identity inside someone else's domain. Three practical differences sit behind that impression.
- You own the identity. When you change providers, the address does not change with them, because the address belongs to the domain.
- You control the records. SPF and DKIM on your own domain are yours to edit, which is what lets you send from a mailing service without breaking authentication.
- The mailboxes come with the hosting. Mail is part of the plan rather than a separate per address product, so adding a mailbox for a new staff member is an account change, not a purchase.
Step one: create the mailboxes
In cPanel, open the email section and create an account for each address. Enter the part before the @, choose the domain from the list, set a password, and set a mailbox quota or leave it unlimited. Repeat for each role and each person: hello@, accounts@, orders@, and one per staff member.
Every Australian hosting plan includes unlimited email accounts, so the number of addresses is not the constraint. Three things are worth deciding deliberately at this point.
Forwarders. An address can forward straight to a mailbox you already read, without a full account behind it. Useful for a role you check occasionally. Less useful for anything you need to send from, because a forwarder cannot send.
Autoresponders. An automatic reply, set per address, for a week away or a shutdown period. It is the one piece of setup most small businesses skip and then wish they had not.
Quotas. A quota stops one mailbox growing without limit, which matters for the address that collects invoices and attachments. An address with no quota is a decision, not a default, so make it on purpose.
Mailboxes are read in a browser through webmail in cPanel, or in a mail application over IMAP, using the full address as the username and authentication turned on for the outgoing server. That is what keeps the same mail visible on a laptop and a phone.
Step two: the DNS records that decide delivery
This is the part that gets skipped, and it is the reason legitimate mail ends up in spam. Each record does one job, and a missing one breaks the chain of proof that receiving servers check.
| Record | What it does | What goes wrong without it |
|---|---|---|
| MX | Tells the internet which server receives mail for your domain | Mail bounces, or goes to a mailbox at a provider you thought you had left |
| SPF (a TXT record) | Lists the servers allowed to send mail as your domain | Receiving servers cannot tell your mail from a forgery |
| DKIM (a TXT record) | Publishes a public key so the receiving server can check the signature on your messages | No proof the message came from you or arrived unaltered |
A wrong record is worse than a missing one. An SPF record that no longer lists your sending service will fail your legitimate mail, which looks exactly like being filtered for no reason.
The records are read from whichever nameservers the domain uses, and that is the part people miss. If the domain's nameservers point at a provider you left, editing records in the hosting control panel changes nothing, because nothing is reading them. Before touching a single record, confirm the domain is resolving to the hosting you think it is. Our guide to how to point your domain at your hosting covers that check, and it is worth doing before a migration rather than during one.
Two habits prevent most of the damage. Take a screenshot of the zone before you edit it, because a zone with no copy is a zone you reconstruct from memory at midnight. And change one record at a time, confirming mail still arrives before making the next change.
Why legitimate email lands in spam
The receiving provider decides, not your host, and it works from evidence. When there is no evidence, the default is suspicion. Four causes cover most of it.
No SPF, no DKIM, or one of them wrong. The receiving server has nothing to check the message against, so it treats it as an unknown sender.
Sending through a service the domain does not authorise. A mailing platform or a booking system sends on your behalf without being listed in SPF, so every campaign weakens the domain's standing.
Content and list quality. Bought lists, high bounce rates and spam-shaped content get a domain filtered regardless of how well the records are set up.
A new domain with no sending history. A domain registered last week has no reputation either way. Steady volume from real recipients builds one, and a burst of a thousand messages in week one does not.
The fixes follow the same order: publish correct SPF and DKIM, authorise every service that sends for you, keep lists real, and warm a new domain up gradually.
Mailboxes here, or a separate suite
Every hosting plan includes the mailboxes, so for most businesses the question is settled by the plan they already have. If the team already works inside Google Workspace or Microsoft 365, either can be supplied for your domain, which keeps the address on your domain while the mailbox lives in that suite. That is worth choosing deliberately rather than by default, because mail is the one part of a hosting account that people notice immediately when it misbehaves.
The full list of what comes with a plan, and what is a separate product, is in what is included in web hosting. The plans themselves are on the shared hosting plans that include mailboxes.
Moving email when you change hosts
The address belongs to the domain, so a move keeps the address as long as the domain moves with it. The order of work is what protects the mail.
Create the mailboxes on the new host first. Then change the MX record. Mail sent in between is delivered to whichever server the record points at, so there is no gap as long as the new mailboxes exist before the record moves. Move the records before the mailboxes exist and mail bounces for as long as it takes you to notice.
How to move your website to a new host covers the sequence end to end. If you are moving to us, migration is free when you host with us for at least twelve months.
Frequently asked questions
Do I need a separate email provider, or can my website hosting do this? For most small businesses the hosting does it, because the mailboxes are part of the plan. A separate suite is worth it when the team already works in one and wants the rest of that suite for the same address.
Can I keep my current address if I move hosts? Yes. The address belongs to the domain, so if the domain moves with you the address stays exactly the same.
Will I lose email when I change hosts? Not if the mailboxes exist on the new host before the MX record changes. Set the mailboxes up first, then move the record.
Can I read mail in a browser and on my phone? Yes. Webmail in cPanel covers the browser, and a mail application over IMAP keeps the same mailbox in sync across devices.
What is the difference between a forwarder and a mailbox? A forwarder passes mail to an address you already read and cannot send from itself. A mailbox stores mail on the server, can send, and has a quota.
Why does my mail still go to spam when the records look right? Check that the sending service you use is listed in SPF, that DKIM is signing, and that the domain's nameservers are the ones actually being read. A record edited on the wrong nameservers has no effect at all.
Get email on your domain
If the domain is already registered and pointed at your hosting, the mailboxes are the quick part and the records are the part worth doing carefully. Every Australian hosting plan includes unlimited mailboxes on your own domain, with webmail, IMAP, forwarders and autoresponders.
If you would rather not touch the records, ask us and we will tell you what to change and in what order. Phone 1300 565 610, 9am to 5pm Monday to Friday, or email hello@webhostingpeople.com.au, which is answered 24/7.
Primary action: See what business email hosting includes