Why not Terraform? #3
allixsenos
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
From the perspective of someone who isn't inherently a fan of Terraform, it seems to me that using Terraform for DNS is in the same category as "using Ansible to manage AWS infrastructure"... it's possible, but is it really a good solution? Off the bat, the advantages of dnscontrol:
cloudflare_recordtype resource, and then when you want that in Route53 you need to change the type of record? Dnscontrol keeps that separate, and it's very easy to load a zone from something into something else. People often do that, it helped me for example to migrate an internal domain from Rackspace DNS (yuck) to Route53. Not only are such migrations often done but people often publish the same zone to multiple destinations for fallback... how would you publish the same zone to Cloudflare and Route53 with Terraform, for example?At my old job, we had an application stack that would create a DNS record for the application so that it was available at
appname.dev.internal.domain, that to me is a totally valid use case for TF or whatever you're using for IaC, because it's part of the app stack... my solution is more for things that you would maintain "manually" regardless. And for various, for example, "parked" domains which are a pain in the ass when you start to maintain a hundred of them.Very interested to hear thoughts on this.
Beta Was this translation helpful? Give feedback.
All reactions