Coredns as DNS provider for caddy (going full circle)

stp · August 30, 2016, 11:30am

Just a thought that came up.

One method would probably be to just document on how to use rfc2136 aka dynamic updates.

For some more details on the dns provider side from lego:

go-acme/lego/blob/master/providers/dns/rfc2136/rfc2136.go

// Package rfc2136 implements a DNS provider for solving the DNS-01 challenge using the rfc2136 dynamic update.
package rfc2136

import (
	"errors"
	"fmt"
	"net"
	"strings"
	"time"

	"github.com/go-acme/lego/v4/challenge/dns01"
	"github.com/go-acme/lego/v4/platform/config/env"
	"github.com/miekg/dns"
)

// Environment variables names.
const (
	envNamespace = "RFC2136_"

	EnvTSIGKey       = envNamespace + "TSIG_KEY"

This file has been truncated. show original

This might enable:

ability to enforce changing of the needed TXT record only (whitelist using IP, record, secret, name)
secret/key per domain/webserver