DNSControl Action

Deploy your DNS configuration using GitHub Actions using DNSControl.

Usage

These are the three relevant sub commands to use with this action.

check

Run the action with the 'check' argument in order to check and validate the dnscontrol.js file. This action does not communicate with the DNS providers, hence does not require any secrets to be set.

action "DNSControl check" {
  uses = "koenrh/dnscontrol-action@master"
  args = "check"
}

preview

Run the action with the 'preview' argument to check what changes need to be made. It prints out what DNS records are expected to be created, modified or deleted. This action requires the secrets for the specified DNS providers.

action "DNSControl preview" {
  uses = "koenrh/dnscontrol-action@master"
  args = "preview"
  secrets = ["CLOUDFLARE_API_USER", "CLOUDFLARE_API_KEY"]
}

This is the action you probably want to run for each branch so that proposed changes could be verified before an authorized person merges these changes into master.

push

Run the action with the 'push' arugment to publish the changes to the specified DNS providers.

Running the action with the 'push' argument will publish the changes with the specified DNS providers. You should probably only use this command combined with the GitHub Filters action to make sure that only changes in the master branch are deployed to production.

action "DNSControl push" {
  uses = "koenrh/dnscontrol-action@master"
  args = "push"
  secrets = ["CLOUDFLARE_API_KEY", "CLOUDFLARE_API_USER"]
}

You should probably only use this command combined with the GitHub Filters action to make sure that only changes in the master branch are deployed to production.