MX records changes

[Sandro Santilli]

I've cleaned up the osgeo.org DNS zone so we we now have only 2 MX
records, as the only one needed due to web and mail services for
those hostnames are listening on different iPs:

  - osgeo.org
  - discourse.osgeo.org

The records are now managed via ansible [1] and found in this file:

  deployment/roles/dns-records/tasks/mx.yml

They can be deployed with this command:

  ansible-playbook deployment/deploy-dns-records.yml --tags mx

Optionally, you can add the --check switch to only see if deploying
would change something (although you cannot easily see WHAT, due to
a limitation of the cloudflare ansible plugin [2]):

  ansible-playbook deployment/deploy-dns-records.yml --tags mx --check


[1] https://gitea.osgeo.org/sac/ansible-deployment
    (you need to be SAC to read)
[2] https://github.com/ansible-collections/community.general/issues/10797

--strk; 

  Libre GIS consultant/developer 🎺
  https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20250910/1d3a0a04/attachment.sig>