Create and verify an email forwarder for your domain

An email forwarder receives mail addressed to your domain and sends it to a mailbox you already use. It does not create a separate mailbox here, store a second copy by itself, or provide an authenticated outgoing mail account.

01 Check the mail routing first

Confirm whether the domain already receives email through hosting, Microsoft 365, Google Workspace or another provider. Using a separate forwarding service can require different MX records. Do not replace a working mail provider's MX records until you have decided how every existing address will be handled.

02 Add and verify the address

  1. Open the domain in the client area and select Email Forwarders.
  2. Read any nameserver or service availability message.
  3. Select Add Forwarder.
  4. Enter the part before @, such as sales, in the address field.
  5. Enter the complete destination mailbox in Forwards to.
  6. Save. Check the destination mailbox for the verification message.
  7. Enter the verification code or complete the verification action described in the message. Use Resend code only when needed.
  8. Confirm the forwarder shows a verified or ready state.

03 Test delivery

Send a new message to the domain address from an unrelated external mailbox. Check the destination's inbox and spam folder. Testing only by sending from the destination mailbox can be misleading because some systems treat mail that returns to the sender specially.

If verification arrives but forwarded mail does not, inspect the domain's public MX records and the destination's filtering. Keep the time, sender, recipient and bounce text for support, with private message content removed. Avoid chains that forward through several services or loop back to the original address.

Can I use a catch-all or change the forwarding destination?

Where offered, a catch-all sends unmatched addresses to one mailbox. It also accepts typos and mail to invented addresses, which can increase unwanted messages. Prefer named forwarders when you know the addresses you need.

Changing a destination can require verification again. Removing a forwarder stops that route for new mail; messages already delivered to the destination remain there. If you need to send as [email protected], configure a real mailbox or an authorised sending service separately with its required authentication records.

  • 0 Users Found This Useful
  • domains-dns, domain-nexus
Was this answer helpful?

Related Articles

Back up and restore DNS records

A DNS backup records the zone's entries so you can review or restore a previous configuration....

Use bulk DNS changes across one or several zones

Bulk management is useful when several records need the same new address or TTL. It also...

Add a domain registered elsewhere to your DNS Manager

You can manage DNS for a domain registered with another company when your Nabtech service...

Read a DMARC aggregate report in DNS Manager

The Premium DNS Plus report reader helps you inspect a DMARC aggregate report received from an...

Enable DNSSEC and complete the DS-record setup

DNSSEC lets validating resolvers check signed DNS data against a chain of trust. It needs both...