SPF Records: Add IPv6 (ip6) part to all Local policy frameworks
IPv6 (ip6) additions to domains’ SPF policies (for which Email is Locally Routed) have been completed.
While preparing for the works, we found issues in cPanel’s spf_installer documentation, which we worked with them to get resolved, in order to ensure that we were going to correctly interact with the tool.
That has now been resolved, and following test runs we have now completed the amendments fleet-wide!
Domains with Remote MX (per Email Routing config) should not have had their SPF policy added to.
In such cases, please ensure WordPress/etc is able to email via SMTP-over-IPv6 without issue.
For reference, we used the below cPanel-provided script with the option set 0 0 1.
https://docs.cpanel.net/whm/scripts/the-spf_installer-script/
This was done in a wrapper to obtain each machine’s shared IPv6 /96 prefix, etc.
Questions? Queries? Please get in touch via our Helpdesk. Cheers!
G’day,
We’ll be adding ip6 parts to all existing SPF records to include your shared IPv6 address per-server.
This means amending local in-place Sender Policy Framework (SPF) records, while retaining existing valid parts.
Why are we doing this? For SMTP over IPv6, SPF or DKIM is required, hence this improves deliverability rates.
What if Email Routing is Remote? The utility we’re “wrapping” to achieve this should ignore those Domains.
Questions or concerns? Please reach out so we can assist you.
Cheers,
Merlot Digital
- Managed Servers & WHMCS / Managed Servers (KVM VPS)
- TNC & Merlot (Internal Systems) / Corporate DNS (TNC & Co.)
- TNC & Merlot (Internal Systems) / Corporate Email (& Ticketing)
The Network Crew Pty Ltd (TNC)
Network: AS138521