Using CoreDNS as public authoritative DNS

[alialshamali]

Hi I want to use CoreDNS as a authoritative DNS (name server), I have been trying to figure it out. I want to use etcd as backend for the zone files. I kind of figure out some stuff, but not sure what I am missing. Does anyone have experience with a similar setup?

Here is the config map I am using:

apiVersion: v1
kind: ConfigMap
metadata:
  name: authoritative-coredns
data:
  Corefile: |
    .:53 {
        errors
        log stdout
        health
        etcd  {
          endpoint #endpoints here
          path /authoritative-dns
          TLS etcd_cert etcd_key etcd_ca
        }
        cache
    }
  etcd_ca: "/authoritative-coredns-secrets/etcd-ca"
  etcd_cert: "/authoritative-coredns-secrets/etcd-cert"
  etcd_key: "/authoritative-coredns-secrets/etcd-key"

I am using Kubernetes secrets to load in the etcd certificates as Base64. To make its easier to manage.
Also what would be the sample zone file in etcd for example: example1.com, example2.com

Any help will be appreciated.
Thanks

[miekg]

The etcd plugin doesn't provide all resource type - I'll clarify that in the docs. For now only the file plugin is there for authoritative serving. We had some discussion a while back on making a DB backend and interface a while back.

What problems are you seeing?

[schors]

I'm thinking about this for a while. It may be better to implement the resource records backend, not zones, as is done by CloudFlare

[miekg]

Sounds interesting, do you some details about this? Or open an issue where we can discuss?

[schors]

The basic requirements for implementing the backend:

1. Speed :-)
2. Low latency
3. Online adding, changing and deleting zones
4. Online zone refreshing
5. Selecting for signing or unsigning zones (for secondary zones)

[schors]

Sounds interesting, do you some details about this? Or open an issue where we can discuss?

Open dedicated issue

[alialshamali]

I really like core-dns, and want to figure out if we can replace authoritative DNS with it. I was thinking of using etcd to store the zones so it easy to amend and add zone files. I want to make the service elastic on K8s so you can use the entire cluster incase you need expand the service.

I want to build a test setup and benchmark against NSD / Knot / Bind / Power-DNS and maybe erl-DNS. Also want to figure a way to ensure autoscale for the DNS to ensure it will scale to met the demand.

I believe this a great use case. I will open a new issue

[miekg]

Can't be done with etc, see #1226 for discussion on how to make that possible