Terraform Provider for Hetzner DNS

Read about what I learnt while implementing this Terraform Provider.

This provider is on published on the Terraform registry. You can find resources and data sources documentation there or here.

Requirements

Terraform 0.12.x / 0.13.x
- Read how insekticid migrated from 0.12 to 0.13 in this article.
Go 1.14 (to build the provider plugin)

Installing and Using this Plugin

If you want or need to install the provider locally, take a look at INSTALL. For Terraform <= 0.12 this is required in order to use this provider.

Using Provider from Terraform Registry (TF >= 0.13)

Terraform introduced the Terrafrom registry with version 0.13. This provider is published and available there. If you want to use it, just add the following to your terraform.rf:

terraform {
  required_providers {
    hetznerdns = {
      source = "timohirt/hetznerdns"
      version = "1.0.6"
    }
  }
  required_version = ">= 0.13"
}

Then run terraform init to download the provider.

Install and Use Provider on your Local Machine (TF >=0.13)

After installing the provider as descibed in INSTALL, add the following to your terraform.tf.

terraform {
  required_providers {
    hetznerdns = {
      source = "github.com/timohirt/hetznerdns"
    }
  }
  required_version = ">= 0.13"
}

Authentication

Once installed you have three ptions to provide the required API token that is used to authenticate at the Hetzner DNS API.

Enter API Token when needed

You can enter it every time you run terraform.

Configure the Provider to take the API Token from a Variable

Add the following to your terraform.tf:

variable "hetznerdns_token" {}

provider "hetznerdns" {
  apitoken = var.hetznerdns_token
}

Now, assign the your API token to hetznerdns_token in terraform.tfvars:

hetznerdns_token = kkd993i3kkmm4m4m4

You don't have to enter the API token anymore.

Inject the API Token via the Environment

Assign the API token to HETZNER_DNS_API_TOKEN env variable.

export HETZNER_DNS_API_TOKEN=<your api token>

The provider uses this token and you don't have to enter it anymore.

Example Usage

# Specify a zone for a domain (example.com)
resource "hetznerdns_zone" "example_com" {
  name = "example.com"
  ttl  = 60
}

# Handle root (example.com)
resource "hetznerdns_record" example_com_root" {
  zone_id = hetznerdns_zone.example_com.id
  name    = "@"
  value   = hcloud_server.server_name.ipv4_address
  type    = "A"
  ttl     = 60
}

# Handle wildcard subdomain (*.example.com)
resource "hetznerdns_record" "all_example_com" {
  zone_id = hetznerdns_zone.example_com.id
  name    = "*"
  value   = hcloud_server.server_name.ipv4_address
  type    = "A"
  ttl     = 60
}

# Handle specific subdomain (books.example.com)
resource "hetznerdns_record" "books_example_com" {
  zone_id = hetznerdns_zone.example_com.id
  name    = "books"
  value   = hcloud_server.server_name.ipv4_address
  type    = "A"
  ttl     = 60
}

# Handle email (MX record with priority 10) 
resource "hetznerdns_record" "example_com_email" {
  zone_id = hetznerdns_zone.example_com.id
  name    = "@"
  value   = "10 mail.example.com"
  type    = "MX"
  ttl     = 60
}

lazyfrosch / terraform-provider-hetznerdns