| .. | ||
| msg | ||
| singleflight | ||
| cname_test.go | ||
| etcd.go | ||
| group_test.go | ||
| handler.go | ||
| lookup.go | ||
| lookup_test.go | ||
| multi_test.go | ||
| other_test.go | ||
| path.go | ||
| path_test.go | ||
| README.md | ||
| setup_test.go | ||
| stub.go | ||
| stub_cycle_test.go | ||
| stub_handler.go | ||
| stub_test.go | ||
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...]
zoneszones 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
}
stubzonesenable the stub zones feature.paththe path inside etcd, defaults to "/skydns".endpointthe etcd endpoints, default to "http://localhost:2397".upstreamupstream resolvers to be used resolve external names found in etcd.tlsfollowed the cert, key and the CA's cert filenames.