mirror of
https://github.com/coredns/coredns.git
synced 2025-12-02 00:24:08 -05:00
8f9f2cd1ab
This middleware acts in the same way as SkyDNS. We might add options
to allow it to be behave different, but for now it will suffice.
A Corefile like:
.:1053 {
etcd miek.nl
proxy . 8.8.8.8:53
}
will perform lookup in etcd and proxy everything not miek.nl to Google
for further resolution.
The internal etcd forwarding *also* uses the proxy infrastructure,
meaning you get health check and such for (almost) free
779 B
779 B
etcd
etcd enabled reading zone data from an etcd instance. The data in etcd has to be encoded as
a message
like SkyDNS.
Syntax
etcd [zones...]
zoneszones it 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 round_robin middleware. optimize
middleware?
etcd {
path /skydns
endpoint endpoint...
stubzones
}
path/skydnsendpointendpoints...stubzones