We’ve added an option to specify an optional second master DNS server for zones in our Secondary DNS service. Unlike the first master, only an IPv4 or IPv6 address is accepted for the second master. This can be useful if you want to specify a redundant master server or dual stack IPv6 and IPv4 connectivity for the same master.
Category: IPv6
Categories
New Outbound Mail Features
As we mentioned earlier, there are several new new features for our Outbound Mail service pending imminent release. We’re pleased to announce the release of the following:
- Mail mirroring support for Outbound accounts
- Mail forwarding (BCC) for Outbound accounts
- IPv6 access filter to compliment the existing IPv4 filter
Due to a last minute bug, the following feature will be delayed until May 22:
- Option to send 5xx response for common DNS errors instead of 4xx
For more information on the bug that was discovered, please read post Bug in “Mail Server” Type Outbound Accounts. The IP and DNS related changes would cause these accounts to reject submissions due to missing parameters, so we decided to delay this feature until those affected could be notified.
Categories
Mail Forwarding IPv6 Enabled
As part of our ever expanding quest to fully IPv6 enable our services, the new IPv6 enabled mail forwarding servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.
We’re getting close to tackling the big one: IPv6 enabled incoming mail. Stay tuned!
We are changing the source of forwarded mail as handled by the “Mail Forwarding” option in the account control center. Messages forwarded to external email addresses were previously sent from 208.79.240.32/28. Starting today, we will begin migrating forwarding to a new group of servers out of 208.79.241.112/28. This change is permanent and is being made as part of our recent announcement on enforced content filtering for forwarded mail.
This will also allow us, in the future, to insert forwarding delivery results into the online mail logs. More immediately, these new servers will be also be IPv6 enabled.
[May 8] The IPv6 enabled servers are now online. If a forwarding destination is reachable via IPv6, we’ll try it.
We have begin the process of migrating our legacy IPv6 network into our /32 allocation, 2607:fe70::/32. Once this is complete, we will further enable other services with IPv6, such as incoming mail.
If you’d like to test it, you can use 2607:fe70::1 as a ping or traceroute destination.