Introduction
Integrating TNZ Email with your DNS domain ensures reliable email delivery, bounce management, and adherence to industry email standards.
Follow this guide to configure your DNS records, including SPF, DKIM, and MX records, for a smooth setup.
Choosing a Subdomain for TNZ Email
We recommend using a dedicated subdomain for TNZ Email, such as email.yourdomain.com
This allows TNZ Email to manage the subdomain without interfering with your main domain's email setup.
Why a Subdomain?
- Safeguards your main domain from unintended changes.
- Provides flexibility for email handling and bounce management.
- Ensures emails appear to come from your primary address (e.g.
yourname@yourdomain.com
) while leveraging TNZ’s infrastructure.
Can I use my main domain?
Yes, you can use either a dedicated subdomain, or TNZ can send as your main domain.
If using your main domain, if an email fails to send, the bounce notification will be emailed to your email address (and not processed by TNZ Email).
Smart Configuration using a Subdomain
For simple set-up and bounce tracking, use a dedicated email subdomain.
Log into your DNS Provider
To configure your domain's DNS entries, you'll need to log into your Domain's DNS Provider/Host.
For example, this might be GoDaddy, CloudFlare, 1st Domains, CrazyDomains, FreeParking, etc.
Configure Your CNAME Record
Using a CNAME record inherits the SPF, DKIM, DMARC and MX requirements without needing to manually configure them.
Enter this new DNS record:
- Record Type = CNAME
- Host = [your subdomain, e.g. "email"]
- Value = email.tnz.net.nz
Save the changes.
Sending using the TNZ API
When submitting an email using the TNZ API, use:
SMTPFrom = bounces@your-subdomain.your-domain.com
From = Your Company
FromEmail = your-address@your-domain.com
For example:
{
"MessageData" :
{
"SMTPFrom": "bounces@email.example.com",
"From": "API Sender",
"FromEmail": "noreply@example.com",
}
}
Manual Configuration using my Main Domain
Alternative, use your main domain.
Log into your DNS Provider
To configure your domain's DNS entries, you'll need to log into your Domain's DNS Provider/Host.
For example, this might be GoDaddy, CloudFlare, 1st Domains, CrazyDomains, FreeParking, etc.
Configure Your SPF Record
SPF (Sender Policy Framework) is crucial for preventing email spoofing.
Adding to your SPF record authorises TNZ Email servers (_spf.tnz.co.nz
) to send emails on behalf of your domain.
Edit your existing SPF record:
If you already have an SPF record, simply add "include:_spf.tnz.co.nz" to the value before "all".
Add a new SPF record:
If you do not have an SPF record, add the following:
- Record Type = TXT
- Host = @ (root)
- Value = "v=spf1 mx include:_spf.tnz.co.nz ~all"
Example SPF Record:
Configure Your DKIM Record
DKIM (DomainKeys Identified Mail) cryptographically proves the emails TNZ sends comes from an approved source.
Enter this new DNS record:
- Record Type = CNAME
- Host = TNZMail._domainkey
- Value = TNZMail._domainkey.email.tnz.net.nz
Save the changes.
Configure Your DMARC Record
DMARC (Domain-based Message Authentication, Reporting, and Conformance) provides a reporting source is SPF and DKIM are misaligned.
Edit your existing DMARC record:
If you already have a DMARC record, skip this step.
Add a new SPF record:
If you do not have a DMARC record, enter this new DNS record:
- Record Type = TXT
- Host = _dmarc
- Value = "v=DMARC1; p=none; pct=100"
Save the changes.
Sending using the TNZ API
When submitting an email using the TNZ API, use:
SMTPFrom = your-address@your-domain.com
From = Your Company
FromEmail = your-address@your-domain.com
For example:
{
"MessageData" :
{
"SMTPFrom": "noreply@example.com",
"From": "API Sender",
"FromEmail": "noreply@example.com",
}
}
FAQs
Why should I use a subdomain for TNZ Email?
Using a subdomain isolates your TNZ Email operations, ensuring that changes won't disrupt your primary domain's email services. It also streamlines security and operational flexibility.
What happens if I don’t update my SPF and DKIM records?
Without SPF and DKIM, your emails are more likely to be flagged as spam or rejected by recipient servers. These records authenticate your emails and improve deliverability.
What do the DMARC settings mean?
The DMARC policy specified is relaxed, meaning the p=none tells the receiving email server 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.
Reach out to our technical team for help with this. 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.
What if my domain registrar doesn’t support these settings?
Reach out to your domain registrar's support team or consult with your IT administrator to explore alternative solutions or configurations.