NS records for mesh.nycmesh.net

[james-otten]

Please approve but do not merge until instructed.

Add NS records for the mesh.nycmesh.net zone for the authoritative server nycmesh-713-dns-auth-4 at SN3.

• Add A records for soon to be authoritative server #99 should be merged 3+ hours before this PR is merged.

[zgiles]

Hmm. So redundancy is good, but do we know if the new system nycmesh-713-dns-auth-4 is properly set up? This is the first I've heard of it. What is it running, is it the same setup as the one at sn1, using this repo, how is it routed, etc, or is it something entirely different?

[james-otten]

Hmm. So redundancy is good, but do we know if the new system nycmesh-713-dns-auth-4 is properly set up? This is the first I've heard of it. What is it running, is it the same setup as the one at sn1, using this repo, how is it routed, etc, or is it something entirely different?

This is related to the ongoing project to migrate software services hosted at SN1. I've been trying to increase transparency and maintainability by creating what one might call a "DNS Server factory" with terraform, ansible, and github actions. Thanks to your and others' work on setting up new hardware at new locations, hopefully the investment in IaC will pay off as it becomes easier to reliably create and maintain new DNS servers at new locations.

I have a link to some docs I wrote up on this earlier below. I think you'll notice the decisions that were made to maintain compatibility with existing services and to ensure an easy, phased transition. Check out the infra/ directory in this repository for more specifics on the IaC and server configs. Also, I'm happy to answer any questions you may have (probably slack). Also, you're very welcome to join the beta testers for the recursive resolver in #dns-beta!

https://wiki.mesh.nycmesh.net/books/5-networking/page/dns-beta

I’d like to move this project forward (on the authoritative side) this weekend or next, let me know if you have any concerns with the above.