[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4162: Infrastructure as Code to manage DNS configurations

[Tahoe-LAFS]

#4162: Infrastructure as Code to manage DNS configurations
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:  btlogy
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 To whoever will read this [https://lists.tahoe-lafs.org/pipermail/tahoe-
 dev/2025-August/010133.html update] from the mailing list, we (at Least
 Authority) are waiting for write access to the DNS records of the tahoe-
 lafs.org zone.

 As demonstrated with the `of.tahoe-lafs.org` sub-domain, a delegation from
 Gandi to another DNS hosting provider such as (deSec.io or Hetzner) is
 likely the best option to allow:

 * the current owner(s) of the domain to keep Gandi as the registrar and
 the billing unchanged
 * the current owner(s) to rollback to the current situation by removing
 the delegation if ever needed
 * the members of the community (w/ proper access to the new provider) to
 update the DNS records w/o owning the domain
 * the rest of the community to propose changes the the DNS records via
 pull-requests against the [https://github.com/tahoe-lafs/infrastructure
 tahoe-lafs/infrastructure] repository.

 Alternatively, keeping Gandi for the hosting is also possible, but likely
 more complex (see comment:7)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4162#comment:33>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage