Files
coredns/middleware/etcd
Miek Gieben 0ea2a6088d Add TestServer (#102)
Add a fullblown testing server. This allows us to do integration tests.

Also add a basic proxy test. Further tests will test etcd proxy
and stub zone communication and other "wildish" configurations.
Redo the server startup, so we can access the ports it listens on when
it has started up (with dns.ActivateAndServer).

Extend the .travis file to download etcd and test for that as well.

Put integration tests in test dir
2016-04-10 18:50:11 +01:00
..
2016-03-23 10:41:40 +00:00
2016-03-23 10:41:40 +00:00
2016-04-10 18:50:11 +01:00
2016-03-26 16:29:35 +00:00
2016-04-10 18:50:11 +01:00
2016-04-09 16:17:53 +01:00
2016-03-28 10:49:28 +01:00
2016-04-05 07:37:05 +01:00
2016-04-10 18:50:11 +01:00
2016-04-10 18:50:11 +01:00
2016-03-23 10:41:40 +00:00
2016-03-23 10:41:40 +00:00
2016-04-10 18:50:11 +01:00
2016-04-09 16:17:53 +01:00
2016-04-10 18:50:11 +01:00
2016-03-26 16:29:35 +00:00

etcd

etcd enabled reading zone data from an etcd instance. The data in etcd has to be encoded as a message like SkyDNS.

The etcd middleware makes extensive use of the proxy middleware to forward and query other servers in the network.

Syntax

etcd [zones...]
  • zones zones etcd should be authoritative for.

The will default to /skydns as the path and the local etcd proxy (http://127.0.0.1:2379). If no zones are specified the block's zone will be used as the zone.

If you want to round robin A and AAAA responses look at the loadbalance middleware.

etcd [zones...] {
    stubzones
    path /skydns
    endpoint endpoint...
    upstream address...
    tls cert key cacert
}
  • stubzones enable the stub zones feature.
  • path the path inside etcd, defaults to "/skydns".
  • endpoint the etcd endpoints, default to "http://localhost:2397".
  • upstream upstream resolvers to be used resolve external names found in etcd.
  • tls followed the cert, key and the CA's cert filenames.

Examples