4 ms·
This is great if all your DNS is done via cloud providers like Dyn and Route53, but can I use this to manage zones in traditional DNS instances? I don't see a
by kensey 9y ago
This is great if all your DNS is done via cloud providers like Dyn and Route53, but can I use this to manage zones in traditional DNS instances? I don't see a BIND/dnsmasq/djbdns provider or any code referencing those or other traditional name servers.
- rwmcfa1 9y agoThere is support for sourcing data from djbdns config files, https://github.com/github/octodns/blob/master/octodns/source/tinydns.py https://github.com/github/octodns/blob/master/octodns/source..., but not writing it out to that format currently. It shouldn't be too difficult for someone to add when they have a specific need it. Same goes for other software and providers. There is a PowerDNS provider, https://github.com/github/octodns/blob/master/octodns/provider/powerdns.py https://github.com/github/octodns/blob/master/octodns/provid... which we use for some internal DNS purposes. We actually plan to talk about that in a future post to compliment this one's focus on our external DNS setup. A lot of thought was put into making it relatively easy to add new ones. Writing the tests is generally the most involved part. There's a plan to add a doc on creating a new provider which I/we will hopefully get to soon.