Middleware on Miek Gieben

SkyDNS in CoreDNS

Thu, 24 Mar 2016 18:31:18 +0000

The etcd middleware is shaping up nicely. With the following Corefile you already have a big chunk of the SkyDNS funcionality:

.:1053 {
    errors
    etcd skydns.local
    proxy . 8.8.8.8:53
}

Which says, run on port 1053, accept queries for all zones, if the zone matches skydns.local. go look in etcd, if it doesn’t forward to GOOG. Multiple zones should work as well, but this is not tested as of yet.

Let’s test this with the examples from SkyDNS' README. Let’s add all the rails production sites. (Why does this use rails btw?)

CoreDNS Chaining Middleware

Sat, 19 Mar 2016 20:59:53 +0000

CoreDNS is shaping up nicely and of course the middleware (taken from Caddy) is working great.

Take for instance the following. We want to rewrite ANY queries to HINFO (because DDoS) and then proxy them to Google. We also need some logging. So after downloading and compiling CoreDNS, create the following Corefile:

.:1053 {
    log stdout
    rewrite ANY HINFO
    proxy . 8.8.8.8:53
}

By default CoreDNS will read a file called Corefile, so we can just start it with:

Caddy DNS update

Thu, 17 Mar 2016 22:13:29 +0000

More light!

My “Port Caddy to be a DNS server”-project is alive and kicking. Code will be published soon-ish, mostly waiting for actually naming the bloody thing. Code is also littered with TODOs.

I’ve implemented the following middlewares, the all need tests and actual use, but here we go:

log, for logging (as in Caddy)
error, for error logging (as in Caddy). These both include the {{placeholder}} syntax, so you can use {{port}} and even {>} for logging header bits.
file, really, really stupid zone file backed zone implementation, more a proof of concept
reflect, reflect (test) middleware
proxy, proxy requests to an upstream nameserver/resolver

I also want to add a rewrite middleware that will, for instance, rewrite ANY queries to HINFO ones.