[21.05] Switch MX record for gocept.net

[zagy]

@flyingcircusio/release-managers

FC-23766

Release process

Impact: n/a

Changelog: n/a

PR release workflow (internal)

• PR has internal ticket
• internal issue ID (PL-…) part of branch name
• internal issue ID mentioned in PR description text
• ticket is on Platform agile board
• ticket state set to Pull request ready
• if ticket is more urgent than within the next few days, directly contact a member of the Platform team

Design notes

• Provide a feature toggle if the change might need to be adjusted/reverted quickly depending on context. Consider whether the default should be on or off. Example: rate limiting.
• All customer-facing features and (NixOS) options need to be discoverable from documentation. Add or update relevant documentation such that hosted and guided customers can understand it as well.

Security implications

• Security requirements defined? (WHERE)
  • Keep systems up to date. The old mailserver should be decommissioned.
• Security requirements tested? (EVIDENCE)
  • New server is set up and accepts mail for gocept.net.

[sysvinit]

This change updates the MX record for mail.gocept.net. instead of the top-level MX record for gocept.net.. I presume this is probably not what you intended?

[sysvinit]

(Does mail.gocept.net itself need an MX record? Can we remove that record from the zone file?)