[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:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 Thank you hacklschorsch for those researches.

 Hetzner has confirmed by email that they do support zone only second level
 domain and they do not recommend any changes to our current setup in
 regards with this limitation.

 So, to be complete: an other simple way to become compliant would be to
 delegate the whole domain as initially planned (see draft PR in
 [https://github.com/tahoe-lafs/infrastructure/pull/49
 infrastructure/pull#49])

 One side effect of having the NS records available in the zone of the 2nd
 level domain and absent from the sub one is to fail scanning tool such as
 this one:

 https://mxtoolbox.com/SuperTool.aspx?action=dns%3aof.tahoe-lafs.org

 Despite the feedback I got from the support of Hetzner, this might become
 a problem indeed.

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