Connecting TNZ Email to your domain improves deliverability, security, and bounce handling.
There are two ways to set this up:
| Option |
Best For |
Difficulty |
Bounce Handling |
Subdomain (email.company.com) * Recommended |
Most Users |
Easy |
Fully handled by TNZ |
Main domain (company.com) |
Advanced Setups |
Medium |
Bounces go to your inbox |
Option 1: Use a Subdomain
Example Subdomain: email.company.com
This lets TNZ manage email technical settings without affecting your normal email.
Why is this better?
- Protects your main domain email setup
- Simplifies DNS configuration
- Easier to track TNZ Email versus other email
- TNZ automatically handles bounces
- Still send emails as name@company.com
Step 1: Log into your DNS Provider
This is where your domain DNS is managed.
For example, GoDaddy, Cloudflare, CrazyDomains, 1st Domains, FreeParking, etc.
Step 2: Add a CNAME Record
This single record lets TNZ manage SPF, DKIM, DMARC and bounce routing automatically.
| Setting |
Value |
| Record Type |
CNAME |
| Name (Host) |
email |
| Value (Points To) |
email.tnz.net.nz |
Save the new entry.
Step 3: Advise TNZ
Contact support@tnz.co.nz and advise the CNAME has been added. The team will manually validate the settings are correct and approve the use of the subdomain for your account.
Option 2: Use Your Main Domain
Example Domain: company.com
⚠️ Important: TNZ cannot automatically process bounces. Failed emails will send bounce messages to your inbox.
Step 1: Log into your DNS Provider
This is where your domain DNS is managed.
For example, GoDaddy, Cloudflare, CrazyDomains, 1st Domains, FreeParking, etc.
Step 2: Update SPF Record
SPF authorises TNZ to send email for your domain.
If you DO already have an SPF Record
Add this to your existing record: include:_spf.tnz.co.nz
If you DON'T already have an SPF Record
| Setting |
Value |
| Record Type |
TXT |
| Name (Host) |
@ |
| Value |
v=spf1 mx include:_spf.tnz.co.nz ~all |
⚠️ Warning: Using this value will block other systems from sending email as your domain. This may be positive (it will block potential spammers), however, it may block intentional email too.
Step 3: Add DKIM Record
DKIM proves emails really came from TNZ.
| Setting |
Value |
| Record Type |
CNAME |
| Name (Host) |
TNZMail._domainkey |
| Value |
TNZMail._domainkey.email.tnz.net.nz |
Step 4: Add DMARC Record
DMARC helps monitor email security. If you already have a DMARC record, skip this step.
| Setting |
Value |
| Record Type |
TXT |
| Name (Host) |
_dmarc |
| Value |
v=DMARC1; p=none; pct=100 |
This is a monitoring-only policy. You can enforce stricter rules later.
Step 5: Advise TNZ
Contact support@tnz.co.nz and advise the DNS changes have been made. The team will manually validate the settings are correct and approve the use of the domain for your account.
FAQs
Why is the subdomain option recommended?
It keeps your main email safe, simplifies setup, and lets TNZ manage bounces automatically.
What happens if SPF or DKIM are missing?
Emails may be marked as spam or rejected. Email providers like Gmail and Outlook are strictly enforcing the use of SPF, PTR and DKIM.
What does p=none in DMARC mean?
It means monitor only. No emails are blocked (yet). The p=none tells the receiver to not enforce a policy.
To enhance security, you should gradually work towards an enforced policy, such as p=quarantine; pct=100, meaning quarantine all emails that do not comply with SPF and DKIM.
Useful tools include DMARCian and MailHardener.
How do I confirm my DNS changes were successful?
You can use online DNS lookup tools (MXToolbox) to ensure your SPF, DKIM, and MX records are correctly configured.
Can TNZ help with setup?
Yes, contact TNZ support if you'd like us to check your DNS.
Best API Settings to Use
When sending emails using the TNZ API, set these variables:
Using a Subdomain
SMTPFrom = bounces@email.company.com
From = Your Company
FromEmail = user@company.com
{
"SMTPFrom": "bounces@email.company.com",
"From": "Your Company",
"FromEmail": "user@companycom",
}
Outputs: "Your Company" <user@company.com>
Using Your Main Domain
SMTPFrom = user@company.com
From = Your Company
FromEmail = user@company.com
{
"SMTPFrom": "user@company.com",
"From": "Your Company",
"FromEmail": "user@companycom",
}
Outputs: "Your Company" <user@company.com>