terraform-aws-route53
octoDNS
Our great sponsors
| terraform-aws-route53 | octoDNS | |
|---|---|---|
| 2 | 13 | |
| 121 | 2,972 | |
| 1.6% | 1.7% | |
| 4.5 | 9.3 | |
| about 2 months ago | 11 days ago | |
| HCL | Python | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-aws-route53
-
Converting BIND DNS zones to HCL
Use a module my Reddit friend: https://github.com/terraform-aws-modules/terraform-aws-route53
-
Optional value in for each loop
I want to store Route53 entries in a YAML file. However, I'm accounting for records that can also be an alias to let's say an ELB. The code only works if the entries in the YAML file is of one specific type, "record" or "alias." I'm using the following module - https://github.com/terraform-aws-modules/terraform-aws-route53/blob/master/modules/records/main.tf
octoDNS
- Show HN: WireHub – easily create and share WireGuard networks
- OctoDNS: Tools for managing DNS across multiple providers
-
What is the best way to integrate the bind9 service on ci/cd?
Change to a supported provider for octoDNS. I've done some automating of bind files using Jinja2/Ansible, but I had to roll my own.
-
Converting BIND DNS zones to HCL
I'd use OctoDNS with the ZoneFileSource to parse the zone files into the YAML files so I have structured data to work with, then I'd write a script to loop through each one and generate the above var.records data structure for each
-
The Dhall Configuration Language
We use https://github.com/octodns/octodns for some of our DNS records. It's flexible, much faster than Terraform for thousands of records, and the maintainer Ross has been responsive on issues and pull requests. Also see Cloudflare's blog for how they use it
-
Some of the popular DNS management services as a self hosted service
OctoDNS https://github.com/octodns/octodns
- DNSControl - the most underrated DNS tool
- AWS is down! Half of the internet is down!
-
Akamai Edge DNS Down
Have them all hot and live rather than any sort of failover system. Keep everything in sync with OctoDNS or similar
https://github.com/octodns/octodns
-
Sync Azure DNS zones with onpremise Windows DNS Server
Finally, you could explore the use of third-party sync tools - https://github.com/octodns/octodns might be a good choice.
What are some alternatives?
terraform-aws-lambda - Terraform module, which takes care of a lot of AWS Lambda/serverless tasks (build dependencies, packages, updates, deployments) in countless combinations 🇺🇦
DnsControl - Infrastructure as code for DNS!
aws-eks-base - This boilerplate contains terraform configurations for the rapid deployment of a Kubernetes cluster, supporting services, and the underlying infrastructure in AWS.
DomainMOD - DomainMOD is an open source application written in PHP & MySQL used to manage your domains and other internet assets in a central location. DomainMOD also includes a Data Warehouse framework that allows you to import your web server data so that you can view, export, and report on your live data.
terraform-aws-iam - Terraform module to create AWS IAM resources 🇺🇦
lexicon - Manipulate DNS records on various DNS providers in a standardized way.
terraform-aws-s3-cloudfront-static-website - Terraform Module for an Amazon Static Website using a private S3 bucket and CloudFront.
Designate - OpenStack Technical Committee Decisions. Mirror of code maintained at opendev.org.
aws-terrajet - Terraform template built for AWS. Help Developers deploy their monolith application to AWS in the easiest and fastest way 🚀
dnstwist - Domain name permutation engine for detecting homograph phishing attacks, typo squatting, and brand impersonation
desec-stack - Backbone of the deSEC.io Free Secure DNS Hosting Service
ens - Implementations for ENS core functionality: The registry, registrars, and public resolvers.