Suped

How to set up DMARC/DKIM/SPF for Australian Private Networks

Published 21 Nov 2026
Updated 21 Nov 2026
10 min read
Summarize with
Australian Private Networks email authentication with SPF, DKIM, and DMARC.
To authenticate email sent through Australian Private Networks (APN), authorize its confirmed outbound servers in SPF, enable DKIM signing for your sending domain, and publish DMARC at that domain's _dmarc DNS name. DMARC passes when SPF or DKIM passes with domain alignment to the visible From address.
I first check that APN actually relays the email. An APN internet connection or source label alone does not establish which service needs configuring. Use a received message's headers to confirm the sending path before changing DNS.

Add your domain

The APN website lists connectivity services and Customer Support. I found no public APN custom-domain authentication instructions specifying an SPF include, DKIM selector, or verification screen. Obtain those values for your account through APN support.
  1. Confirm the route. Send a message through your normal application. Check the recipient server's Received headers and authentication results. If APN only provides internet access, configure the mail service that actually sends the message.
  2. Request provisioning. Ask APN to authorize your domain for the outbound service. Request a custom envelope sender, also called MAIL FROM or return path, under your domain, such as bounce.example.com.
  3. Collect exact values. Request the supported SPF mechanism or outbound IP addresses, DKIM signing details, and any DNS records needed for return-path routing. Have APN confirm custom return-path activation for your account.
  4. Verify ownership. If APN supplies a TXT or CNAME ownership challenge, publish its exact name and value at your authoritative DNS host. Request confirmation that the domain is authorized before sending production email.
Make these changes for a domain you control. APN controls authentication records for its own email domains; a customer cannot publish records for a provider-owned address.
Keep existing inbound MX records unless APN explicitly requires a routing change. A custom bounce subdomain can have separate routing requirements without changing delivery for your main domain.
Use account-specific authorization
Do not guess an include:apn.net.au mechanism or copy APN's corporate SPF record. Neither establishes authorization for your customer sending service. Use only the values APN confirms for that service.

Set up SPF

SPF is checked against the envelope sender domain, normally shown in the delivered Return-Path header. If APN uses bounce.example.com, publish or delegate SPF there. An SPF record at example.com does not automatically cover its subdomains.
  1. Read existing DNS. Look up TXT records at the exact envelope sender domain. Edit the existing v=spf1 record if one exists; publish only one SPF record at each name.
  2. Authorize APN. Merge APN's confirmed include mechanism or ip4/ip6 entries into that record before its final all mechanism. Preserve other legitimate senders.
  3. Check lookup limits. Keep evaluation within SPF's limit of 10 lookup-causing terms, including nested includes. Remove obsolete authorizations rather than authorizing APN's entire network.
  4. Confirm domain alignment. Have APN use the configured custom return path. With relaxed SPF alignment, bounce.example.com matches a visible From domain of example.com. Strict alignment requires identical domains.
If APN supplies a CNAME delegation for the return-path hostname, follow that delegation instead of adding TXT records at the same name. A CNAME cannot coexist there with an SPF TXT record. Enter the envelope sender domain into the checker below.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
I confirm the result with a fresh message after APN activates the return path. Changing a display From address or manually inserting a Return-Path header does not configure the SMTP envelope sender.
The record below demonstrates SPF syntax only. 192.0.2.10 is a documentation address, not an APN sending IP. Replace it with APN-confirmed authorization before publishing.
SPF syntax example, not an APN recorddns
bounce.example.com. 3600 IN TXT "v=spf1 ip4:192.0.2.10 -all"

Set up DKIM

DKIM needs an active signer and a matching public DNS key. Ask APN whether its relay signs customer-domain email, or arrange signing on your own sending server before the message reaches APN.
  1. Request signing details. Obtain the signing domain, selector, and exact public-key TXT value or CNAME target. Request a 2048-bit RSA key where supported. Keep the private key on the signing server.
  2. Publish the selector. Add the supplied record at selector._domainkey.yourdomain. Use the actual selector and domain, and check whether your DNS editor appends the zone name automatically.
  3. Activate signing. Ask APN or your mail administrator to enable signing after the DNS record resolves. Publishing a key alone does not make a relay sign messages.
  4. Test a received message. Require dkim=pass and check the DKIM-Signature d= domain against the visible From domain. Read s= to identify the selector actually used.
A passing signature for apn.net.au does not provide DKIM alignment for example.com. With relaxed alignment, the signing domain and visible From domain must share the same organizational domain.
Choose the signing location based on APN's confirmed service capabilities. Test the final received message because relay changes to signed content can invalidate a signature.
APN signs the message
APN holds the signing key and supplies your DNS record. Have APN confirm the customer signing domain and activation, then verify the recipient reports dkim=pass for that domain.
Your server signs first
Your mail administrator manages the signing key and selector. Sign before relaying through APN, then verify that the signature survives delivery. Use this approach if APN does not provide customer-domain signing.

Set up DMARC

Publish DMARC for the domain in the visible From address. For sender@example.com, the DNS name is _dmarc.example.com. Do not publish your policy under apn.net.au or only under a separate bounce domain.
  1. Inspect the current policy. Read the existing DMARC TXT record. Keep p=quarantine or p=reject if already deployed; do not downgrade it to configure APN.
  2. Build a new policy. If no policy exists, use p=none while you validate every sender. Our DMARC record generator creates the TXT value with your chosen reporting address.
  3. Set the report destination. Replace dmarc@example.com with a working mailbox or assigned aggregate-report address. For an external reporting domain, ensure that the report receiver authorizes reports for your domain.
  4. Publish one record. Add or edit the single DMARC TXT record at _dmarc. Preserve existing reporting destinations and alignment settings unless you intentionally change them.
Enter the visible From domain into the DMARC checker after saving DNS. Check the published policy and reporting destination, including whether the DNS editor accidentally duplicated the domain suffix.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
A valid DMARC record confirms policy publication. A fresh received message establishes whether APN traffic actually passes SPF or DKIM with the required domain alignment.
For a domain without an existing policy, start with the exact value below and replace the example domain and reporting mailbox. p=none requests monitoring without requesting quarantine or rejection under DMARC.
Starting DMARC record
New policy exampletext
Host: _dmarc.example.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com
Keep an existing quarantine or reject policy. Resolve APN authentication issues on the sending service while retaining that protection.

Verify and troubleshoot

I test the same application and relay used in production. A test from another mailbox or sending service does not establish that the APN route is configured correctly.
The email tester is the quickest message-level check. Send an email through APN to the address the widget provides, then review its authentication diagnosis. Repeat after correcting a failure.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
Read Authentication-Results added by the receiving system. Compare smtp.mailfrom with the visible From domain for SPF, and the passing signature's d= domain with From for DKIM.
If APN still uses its own return path, an SPF pass for that provider domain does not supply SPF alignment for yours. Passing DKIM with domain alignment still passes DMARC, but fix the custom return path if your account is intended to use it.
  1. Resolve DNS failures. Check the authoritative zone, record names, and cached TTLs. Merge duplicate SPF records and correct missing or malformed DKIM selector records.
  2. Inspect message changes. For DKIM body-hash failures, check whether a relay or application modifies signed content. Test after the final modification point.
  3. Check forwarding separately. Forwarding commonly breaks SPF. Verify that a signature with domain alignment survives the forwarded route before relying on SPF-only authentication.
  4. Retest every route. Check normal mail and automated messages, including any secondary outbound route. Save full headers with the failure when escalating to APN.
DNS checks, replace the domain and SELECTORbash
dig +short NS example.com dig +short TXT bounce.example.com dig +short CNAME bounce.example.com dig +short TXT SELECTOR._domainkey.example.com dig +short CNAME SELECTOR._domainkey.example.com dig +short TXT _dmarc.example.com

Get alerted when it breaks

Suped is our DMARC reporting and email authentication platform. Its DMARC monitoring connects APN authentication failures to sending sources and steps to fix them, so the setup remains monitored after the initial test.
  1. Verify the source. In Suped's Sources view, confirm that APN traffic belongs to your service before marking it verified. Compare sending IPs and authentication domains with APN's confirmed configuration.
  2. Enable issue notifications. In Notifications, enable Issues detected and Sending sources need verification. Configure DMARC summary emails for ongoing review.
  3. Investigate changes. Open affected records in Detail view to inspect SPF and DKIM results. Use DNS history to check whether a record change preceded the failure.
  4. Verify the repair. Follow the issue's Steps to fix, apply the correction at the responsible DNS host or sending server, and verify the issue again. Send a fresh test through APN.
Report-based monitoring requires aggregate reports to reach Suped's assigned reporting address. A standalone dmarc mailbox does not automatically supply data to the platform.
Issue alerts depend on the data available when a problem is detected. Aggregate reports commonly arrive daily, so I use a fresh message test for immediate verification after DNS or relay changes.

Secure your domain with p=reject

Move to p=reject after all legitimate sending routes pass DMARC consistently. I review each authorized source separately because a high overall pass rate can hide failures in a low-volume billing or support system.
  1. Review the inventory. Use Suped's verified and unverified source views to account for APN and every other legitimate sender. Do not authorize an unfamiliar source solely to eliminate a failure.
  2. Fix legitimate failures. Use Suped's record diagnostics to correct authorization and domain alignment. Prefer passing DKIM as well as SPF so forwarded mail has a viable authentication path.
  3. Stage enforcement. For a new deployment, move from p=none to p=quarantine after testing. Review reports across a complete business sending cycle, including infrequent mail, before advancing.
  4. Apply rejection. Change the existing policy to p=reject, keep aggregate reporting active, and continue monitoring legitimate failures. Review subdomain policy inheritance before saving.
Suped's hosted DMARC lets you manage policy changes through the dashboard once configured. Use its source diagnostics and notifications to assess each enforcement change, then keep monitoring after rejection is enabled.

Policy

Requested handling

Advance when

p=none
Monitor
Senders identified
p=quarantine
Treat failures as suspicious
Legitimate routes validated
p=reject
Reject failures
Continue monitoring
DMARC enforcement stages
The example below changes only the policy and retains reporting. Replace the reporting mailbox with your active destination; preserve any other intentional tags in your existing record.
DMARC rejection policy exampletext
Host: _dmarc.example.com Type: TXT Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Without a separate subdomain policy or an applicable explicit DMARC record, the organizational domain's policy also affects subdomain mail. Check those sending routes before enforcing rejection.
p=reject requests rejection of messages that fail DMARC. Receivers retain local discretion, and authentication does not guarantee inbox placement. Keep message testing and report review in the change process for future relay or key updates.

Frequency asked questions

Obtain the exact mechanism or outbound IP addresses from APN for your sending service. No universal customer SPF include was established from its public documentation. Do not assume include:apn.net.au is valid. Publish authorization at the domain used in the SMTP envelope sender.

An rDNS hostname ending in apn.net.au suggests Australian Private Networks infrastructure. Confirm the exact sending IP and relay with APN. The suffix is a source-identification clue, not proof that a message is authorized for your domain; verify SPF, DKIM, and DMARC results.

SPF can pass for APN's envelope sender domain while the visible From address uses your domain. That does not provide SPF domain alignment. Configure your custom return path or obtain a passing DKIM signature with domain alignment. DMARC passes when either authentication path meets both requirements.

Sign on your own sending server before relaying through APN, and verify that the signature survives delivery. SPF with domain alignment can pass DMARC without DKIM, but forwarding commonly breaks SPF, so test forwarded routes before enforcing a policy.

Keep an existing p=reject or p=quarantine policy. Configure and test the APN sending route before using it for production. The p=none starting record is for a domain that has no established enforcement policy.

Check the authoritative DNS records immediately, then allow existing cached answers to expire according to their TTLs. Send a new message after the records resolve correctly and APN activates the service changes. Aggregate reporting commonly follows a daily schedule, so reports are slower than a message test.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing