History

Miek Gieben 9c62ddaa01 Small golint cleanup (#977 ) * Small golint cleanup Mostly docs in autopath. * duh		2017-08-24 08:56:48 +01:00
..
autopath.go	Small golint cleanup (#977 )	2017-08-24 08:56:48 +01:00
autopath_test.go	mw/autopath: integration test with erratic (#930 )	2017-08-18 12:57:23 +01:00
cname.go	WIP: autopath as middleware (#859 )	2017-08-09 03:13:38 -07:00
README.md	mw/autopath: a minimal bug section (#961 )	2017-08-21 08:57:54 +01:00
setup.go	core: hide registerHandler (#964 )	2017-08-22 14:21:42 +01:00
setup_test.go	mw/autopath: integration test with erratic (#930 )	2017-08-18 12:57:23 +01:00

README.md

autopath

The autopath middleware allows CoreDNS to perform server side search path completion. If it sees a query that matches the first element of the configured search path, autopath will follow the chain of search path elements and returns the first reply that is not NXDOMAIN. On any failures the original reply is returned.

Because autopath returns a reply for a name that wasn't the original question it will add a CNAME that points from the original name (with the search path element in it) to the name of this answer.

Syntax

autopath [ZONE..] RESOLV-CONF

ZONES zones autopath should be authoritative for.
RESOLV-CONF points to a resolv.conf like file or uses a special syntax to point to another middleware. For instance @kubernetes, will call out to the kubernetes middleware (for each query) to retrieve the search list it should use.

Currently the following set of middleware has implemented autopath:

kubernetes
erratic

Examples

autopath my-resolv.conf

Use my-resolv.conf as the file to get the search path from. This file only needs so have one line: search domain1 domain2 ...

autopath @kubernetes

Use the search path dynamically retrieved from the kubernetes middleware.

Bugs

When the cache middleware is enabled it is possible for pods in different namespaces to get the same answer.