Setting Up Your Domains DNS For TNZ Email

Improve email deliverability with TNZ Email DNS setup. Learn how to configure SPF, DKIM, DMARC, and subdomains for secure sending and proper bounce handling.

Connecting TNZ Email to your domain improves deliverability and routes bounce messages correctly. It also stops other people from spoofing your domain. Without the right DNS records, emails often land in spam or get rejected outright by Gmail, Outlook, and other major providers.

There are two ways to set this up.

âš™ī¸ Which Option to Choose

✅ Subdomain (Recommended)

email.company.com

  • Best for: most users
  • Difficulty: easy
  • Bounces: fully handled by TNZ
  • Protects your main domain email setup
  • Only two DNS records to add

đŸ› ī¸ Main Domain

company.com

  • Best for: advanced setups
  • Difficulty: medium
  • Bounces: go to your inbox
  • Touches your existing email setup
  • Four DNS records to add or update

Short version: pick the subdomain option unless you have a specific reason not to. It's quicker, safer for your existing email, and TNZ handles bounces for you.

🚀 Before You Start

You'll need:

  • Admin access to your DNS provider (where your domain is managed, such as GoDaddy, Cloudflare, 1st Domains, or FreeParking).
  • About 10 minutes to add the records.
  • Patience for DNS propagation. Changes often appear on major platforms within minutes but it can take up to 24 hours for the entire internet to catch up.

A quick glossary before the steps:

🔗
CNAME

A DNS record that points one name at another.

âœ‰ī¸
SPF

Tells receiving servers which senders are allowed to send email for your domain.

🔐
DKIM

Attaches a cryptographic signature so receivers can verify emails really came from TNZ.

📊
DMARC

Tells receivers what to do when SPF or DKIM fail, and lets you monitor results.

✅ Option 1: Use a Subdomain (Recommended)

Example subdomain: email.company.com

This lets TNZ manage the email-specific DNS settings on a dedicated subdomain, without touching your normal email setup. You still send as name@company.com, so recipients see your main address.

Benefits:

  • Protects your main domain email setup
  • Simpler DNS configuration (two records)
  • Easier to track TNZ Email separately from other email
  • TNZ handles bounces automatically

Step 1: Log into your DNS provider

Open the dashboard where your domain's DNS is managed. Most providers call this area "DNS", "DNS Management", "Zone File", or "Nameservers".

Common providers: GoDaddy, Cloudflare, CrazyDomains, 1st Domains, Domainz, FreeParking.

Step 2: Add a CNAME record for the subdomain

This record lets TNZ manage SPF and bounce routing automatically.

Record type CNAME
Name (Host) email
Value (Points to) email.tnz.net.nz

Save the record.


Step 3: Add a CNAME record for DKIM

This record lets TNZ sign outgoing emails on your behalf.

Record type CNAME
Name (Host) TNZMail._domainkey.email
Value (Points to) TNZMail._domainkey.email.tnz.net.nz

Save the record.

Step 4: Let TNZ know

Email support@tnz.co.nz to say the CNAMEs are in place. The team will verify the settings and approve your subdomain for sending.

Once approved, emails will send with:

  • SMTP From = bounces@email.yourcompany.com (what mail servers see)
  • From Email = your.name@yourcompany.com (what recipients see)

đŸ› ī¸ Option 2: Use Your Main Domain

Example domain: company.com

Step 1: Log into your DNS provider

Same as Option 1. Find your DNS management area at GoDaddy, Cloudflare, 1st Domains, or wherever your domain lives.

Step 2: Update your SPF record

SPF authorises TNZ to send email on behalf of your domain. A domain can only have one SPF record, so if you already have one, add to it rather than replace it.

If you already have an SPF record

Find the existing TXT record starting with v=spf1 and add include:_spf.tnz.co.nz before the ~all or -all at the end.

📋 Example: Merging with an existing SPF record

Before: v=spf1 include:_spf.google.com ~all

After: v=spf1 include:_spf.google.com include:_spf.tnz.co.nz ~all

If you don't have an SPF record
Record type TXT
Name (Host) @
Value v=spf1 mx include:_spf.tnz.co.nz ~all

Step 3: Add a DKIM record

DKIM proves emails really came from TNZ.

Record type CNAME
Name (Host) TNZMail._domainkey
Value (Points to) TNZMail._domainkey.email.tnz.net.nz

Step 4: Add a DMARC record

DMARC monitors email security and reports on SPF and DKIM results. If you already have a DMARC record, skip this step.

Record type TXT
Name (Host) _dmarc
Value v=DMARC1; p=none; pct=100

p=none is monitor-only, so no emails are blocked. You can tighten this later once you're confident everything is signing correctly.

Step 5: Let TNZ know

Email support@tnz.co.nz to say the DNS changes are done. The team will verify and approve your domain.

🔧 Verify Your DNS Is Live

DNS changes can take a few minutes, or up to 24 hours, to propagate. To check whether your records are visible to the wider internet:

1. Go to MXToolbox.
2. Run a CNAME Lookup for email.yourcompany.com (Option 1) or a TXT Lookup for yourcompany.com (Option 2).
3. Confirm the result matches the values in the tables above.

⚡ API Settings

When sending via the TNZ API, set these variables.

Using a subdomain

{
    "SMTPFrom": "bounces@email.company.com",
    "From": "Your Company",
    "FromEmail": "user@company.com"
}

Output: "Your Company" <user@company.com>

Using your main domain

{
    "SMTPFrom": "user@company.com",
    "From": "Your Company",
    "FromEmail": "user@company.com"
}

Output: "Your Company" <user@company.com>

❓ Frequently Asked Questions

Why is the subdomain option recommended?

It keeps your main email separated from TNZ Email, simplifies setup, and lets TNZ handle bounces automatically. Most businesses have nothing to gain from using the main domain.

How long does DNS propagation take?

Usually a few minutes. Sometimes up to 24 hours, depending on your provider's TTL (time-to-live) settings.

Can I switch between the main domain and subdomain option later?

Yes. You can change these settings at any time.

What happens if SPF or DKIM are missing?

Emails may be marked as spam or rejected. Gmail and Outlook now strictly enforce SPF, PTR, and DKIM for bulk senders.

What does p=none in DMARC mean?

Monitor-only. Receivers report back but don't block anything. Once you're confident TNZ and your other senders are aligned, move to p=quarantine; pct=100 and eventually p=reject. Tools like DMARCian and MailHardener help with the reporting.

How do I confirm my DNS changes worked?

Use MXToolbox to check SPF, DKIM, and CNAME records. TNZ support will also verify before enabling your account.

Can TNZ help with the setup?

Yes. Email support@tnz.co.nz with your DNS provider name and we'll walk through it.

📞 Need More Help?

Visit the TNZ Help Centre or contact the TNZ support team.

Email Support →


Topics:   Email Installation

Start your free trial today!

Ready to revolutionise your messaging?
Connect with people anywhere - boost engagement, responses and conversations.

20 credits over 14-days. No obligation. No credit card required.