CoreDNS is a DNS server that chains plugins

cncf coredns dns-server go plugin service-discovery

Find a file

Miek Gieben 78b4eca181 Not used		2016-03-19 07:46:12 +00:00
core	Use context.Context	2016-03-19 07:32:50 +00:00
middleware	Use context.Context	2016-03-19 07:32:50 +00:00
server	Use context.Context	2016-03-19 07:32:50 +00:00
.gitignore	First commit	2016-03-18 20:57:35 +00:00
.travis.yml	travis	2016-03-19 07:37:20 +00:00
build.bash	First commit	2016-03-18 20:57:35 +00:00
Caddyfile-simple	First commit	2016-03-18 20:57:35 +00:00
CONTRIBUTING.md	Cleanups, removing Caddy name a bit more	2016-03-19 07:42:21 +00:00
Corefile	An example	2016-03-18 21:36:42 +00:00
Corefile-name-alone	First commit	2016-03-18 20:57:35 +00:00
db.dns.miek.nl	First commit	2016-03-18 20:57:35 +00:00
db.miek.nl	First commit	2016-03-18 20:57:35 +00:00
LICENSE	Cleanups, removing Caddy name a bit more	2016-03-19 07:42:21 +00:00
main.go	First commit	2016-03-18 20:57:35 +00:00
main_test.go	First commit	2016-03-18 20:57:35 +00:00
README.md	An example	2016-03-18 21:36:42 +00:00

README.md

CoreDNS

CoreDNS is DNS server that started as a fork of Caddy. It has the same model: it chains middleware.

It is in the early stages of development on should be used on production servers. For now most documentation is in the source and some blog articles can be found here.

https://caddyserver.com/ is also full of examples on how to structure a Corefile (renamed from Caddyfile when I forked it).

Resolver

Start a simple resolver (proxy):

Corefile contains:

.:1053 {
    proxy . 8.8.8.8:53
}

Just start CoreDNS: ./coredns. And then just query on that port (1053), the query should be forwarded to 8.8.8.8 and the response will be returned.