octodns/dyn repository overview

⁠octodns docker images

OctoDNS is DNS as code – a tool for managing DNS across multiple providers⁠.

⁠Usage

$ docker run -v "$(pwd):/octodns" --workdir /octodns octodns/dyn octodns-sync

This runs octodns-sync on the contents of the current working directory.

⁠Flavors

⁠1. 'all'

OctoDNS with all the first-party plugins. See the list in the requirements.txt for the 'all' flavor.⁠.

View on Docker Hub →⁠

⁠2. 'azure'

OctoDNS with only the AzureProvider⁠.

View on Docker Hub →⁠

⁠3. 'cloudflare'

OctoDNS with only the CloudflareProvider⁠.

View on Docker Hub →⁠

⁠4. 'constellix'

OctoDNS with only the ConstellixProvider⁠.

View on Docker Hub →⁠

⁠5. 'digitalocean'

OctoDNS with only the DigitalOceanProvider⁠.

View on Docker Hub →⁠

⁠6. 'dnsimple'

OctoDNS with only the DNSimpleProvider⁠.

View on Docker Hub →⁠

⁠7. 'dnsmadeeasy'

OctoDNS with only the DNSMadeEasyProvider⁠.

View on Docker Hub →⁠

⁠8. 'dyn'

OctoDNS with only the DynProvider⁠.

View on Docker Hub →⁠

⁠9. 'ns1'

OctoDNS with only the Ns1Provider⁠.

View on Docker Hub →⁠

⁠10. 'powerdns'

OctoDNS with only the PowerDNSProvider⁠.

View on Docker Hub →⁠

⁠11. 'route53'

OctoDNS with only the Route53Provider⁠.

View on Docker Hub →⁠

⁠Adding a new flavor

1. Create a new subdirectory, with a requirements.txt file.
2. Specify the dependencies you want in requirements.txt
3. Add GitHub Actions jobs to both workflows for the new flavor

⁠Updating a version

Update the version in all/requirements.txt – it will be used in the 'all' flavor and the provider-specific flavor.