Enable a secondary DNS provider for DDoS resistance
We currently utilize Amazon's Route 53 as a DNS service we will be transitioning to a different primary provider (DynDNS) and have Route53 as a secondary provider; managed and synced by [OctoDNS](https://github.com/github/octodns) via GitLab repositories and CI jobs.
- [x] Establish DynDNS Contract.
- [x] Create Route53 user w/ scoped permissions and access tokens for automation.
- [x] Create DynDNS user w/ API tokens for automation.
- [x] Slurp Route53 zone data into DynDNS using OctoDNS.
- [x] Validate DynDNS data in all zones.
- [x] Test OctoDNS generated changes for population into DynDNS & Route53.
- [ ] Change SOA & NS records for all zones.
- [x] Automate CI job for OctoDNS commits.
- [ ] Generate runbook documentation.
Risk Assessment (r-21)
issue