Set up an email forwarding address for your custom domain

If you want to set up an email forwarding address for your custom domain, think of it as a digital signpost: mail sent to alice@yourbrand.au can land in an inbox you already trust. It suits a Melbourne retailer wanting a public contact address without exposing a founder’s personal Gmail account.

You will need control of the domain’s DNS, a destination inbox and a provider that supports inbound routing. Australian businesses often use a .com.au or .au domain, so confirm eligibility with the registrar before changing nameservers. Forwarding alone does not create an outbound mailbox.

A simple alias works for forms, customer support and password resets. Shared inboxes, calendars and sent mail require a hosted email service or business suite. Choose based on whether the address is a temporary shield, a team channel or the foundation of consistent branded communication.

Australian privacy and billing matter too. If your organisation is covered by the Privacy Act 1988, handling personal information should align with the Australian Privacy Principles; marketing messages also need a lawful basis and working unsubscribe route. Check whether overseas software bills include GST or charge in USD, as an Australian card may add a currency-conversion fee.

Routing method Best fit Main setup Main limitation
Serverless inbound routing A few personal aliases MX records and a verified destination inbox No full mailbox; outbound replies need extra configuration
Hosted business suite Shared team addresses and collaboration User accounts, MX records and authentication records Per-user fees and more administration
Specialist mailbox host Aliases, sending and calendars Full DNS and account configuration Ongoing subscription and provider dependency
Self-hosted mail server Maximum infrastructure control Server, TLS, spam filtering and reputation controls High security and maintenance burden

Choose a routing model that fits

Serverless inbound routing is the simplest option for a small set of aliases. It keeps costs and administration low, but it acts mainly as an entry point to an existing inbox rather than a complete mailbox. Catch-all routing saves setup time, although it can attract unwanted mail.

A business suite makes more sense when staff need shared conversations, consistent signatures and individual access. It costs more per user but provides stronger administration. Compare renewal prices, Australian support coverage, data location and export options instead of relying on a discounted first month. For a sole trader, a simple route can be a fair dinkus until volume grows.

Connect the domain to the destination

Sign in to the domain’s DNS zone, whether it is managed by an Australian registrar or an external service such as Cloudflare. Follow the email provider’s published MX records exactly. Remove old or conflicting MX records unless split delivery is explicitly supported, because competing destinations can deliver mail unpredictably.

Verify the destination inbox before creating routes, and use an account controlled by the organisation rather than a forgotten personal mailbox. Avoid auto-responders and loops that generate automated bounces. Lower the existing mail TTL before a planned cutover if the DNS host permits it, then allow the old value to expire before testing.

Create a useful forwarding alias

Start with names that people can read easily, such as contact@, returns@ and support@. For a sole trader, alice@ may feel more personal, while a role address remains useful after staff changes. Keep the local part short enough to print on invoices and include it consistently on the website and order forms.

With Cloudflare Email Routing, add and verify the destination, then create a custom address or catch-all route under Email Routing. Other providers use different menus but the same principle: define the local part, select a verified inbox and publish the required records. Plus addressing, such as support+bills@, can separate topics, but it is not a replacement for a proper alias and is not accepted everywhere.

Catch-all routing is convenient for small businesses, yet it can generate spam and accidental mail to incorrect recipients. Activate filtering before enabling it and monitor delivery volume. Do not use a catch-all for sensitive applications until you have tested how the destination provider handles unknown local parts.

Test delivery and customer journeys

Send each new address a plain message, an attachment and a reply. Check formatting, sender details, delivery time and spam placement at both ends. Deliberately misdirect one test to confirm that the bounce is clear, and verify that password-reset messages reach the destination rather than a quarantine folder.

When testing a retail workflow, use the alias in an order or contact form. If a retailer then rejects a discount, this guide to coupon code problems can help separate a checkout issue from a bad forwarding setup. Record the time, sender and destination so support staff can diagnose unusual deliveries.

Treat forwarding as part of the business’s security and privacy controls. Limit access to the destination, use transport encryption and keep recovery details in a password manager. Do not forward records subject to Australian retention obligations until you have checked the relevant legal and industry requirements.

Separate receiving from sending

An inbound alias does not automatically protect the domain’s sending reputation. If staff will also send from the custom domain, use a hosted mailbox with SPF, DKIM and DMARC configured correctly. A basic forward also does not authenticate replies as the custom domain, so use an SMTP alias feature or hosted mailbox when branded replies are essential.

Set a review schedule for failed deliveries, spam complaints and abandoned aliases. When campaigns begin, measure replies, clicks and conversions rather than treating message volume as success. Before selecting a promotional channel, compare email versus social returns against the business’s goals and tracking capacity, then keep DNS notes and provider access portable.

Use a staged rollout checklist

Run the change during a quiet period and test from a different network. A Melbourne shop owner and a Sydney operations user can each confirm that the same alias behaves correctly. Keep the previous route available until password resets, customer replies and high-volume messages complete without disruption.

Once the route is stable, decide whether it should remain inbound-only or become a full team mailbox. If campaigns are planned, use Kalikalos’s email marketing services to compare providers, then review consent, unsubscribe handling and data storage rather than choosing on list size alone.

Use this sequence: