4 ms·

I added an equivalent script after we moved to Cloudflare. I found it's easy to make a mistake in the Cloudflare DNS web interface, e.g. it's easy to accidental

by yoran 7y ago

I added an equivalent script after we moved to Cloudflare. I found it's easy to make a mistake in the Cloudflare DNS web interface, e.g. it's easy to accidentally remove an entry. Now, at every deploy to production, we do a backup of the DNS configuration on Cloudflare and save it on S3. This hardly costs us anything as each backup is only a small text file. But I now feel much more comfortable when editing our DNS config.

pronoiac 7y ago
For text, I'd lean to preserving that in a git repo instead.
- yoran 7y ago
  Hmmm that's not a bad idea actually. Easy to get a history by looking at the commits. Thanks!
- stevekemp 7y ago
  Or even use a git-repository as your source of DNS truth! https://dns-api.com/ https://dns-api.com/ is my approach to that problem.
lfaoro 7y ago
Would you like to have the tool automatically export all your DNS records to an S3 bucket? `--export=s3`, `--export=gcs`
nodesocket 7y ago
You can also use Terraform to manage CloudFlare DNS, and you get history, backups, consistency, and change management all for free. Just push the Terraform repo up to GitHub or GitBucket.