Roller NetworkWe have just released a multi-zone settings tool to our Secondary DNS service. This allows settings such as master, second master, and AXFR/NOTIFY settings to be applied to multiple (or all) Secondary DNS zones without having to update each zone individually. Zone file maintenance actions (delete and retransfer) must still be performed individually.
This new feature is available on accounts with Personal Plus or higher.
As we mentioned last week there was a bug preventing us from releasing one of the new features for Outbound Mail. All of the accounts affected by this bug have been contacted and fixed, so we can proceed with the full release on May 22 as promised.
Outbound Mail accounts now feature all of these options:
Our blacklist and whitelist filters have a bulk entry mode that attempts to auto detect the entry type based on a defined pattern. However, you may occasionally want to bulk add something as a specific type without using the auto detect engine, so we have added a new “Entry Type” selector.
As you can see in the example above we also added line numbers to the entry field to make it easier to find lines that throw an error. The auto detect override selector was implemented from a customer feature request.
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.
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:
Due to a last minute bug, the following feature will be delayed until May 22:
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.