This fix tries to address the issue raised in 1275 to clarify
the syntax for multiple endpoints specification.

This fix also adds additional test cases to demo the usage.

This fix fixes 1275.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

Looks like the last commit missed a `~` in the docs.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Add NSID plugin support for CoreDNS

This fix adds NSID plugin support for CoreDNS, as was proposed
in 1256.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Add test cases for NSID plugin
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Generate code for NSID plugin
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Use hostname as the default (as with bind), and remove unneeded copy
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Add README.md
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

When we failing the healthcheck we should increate the fails for this
host; which is the *bleeping* point of doing the HC in the first place.

Add the missing atomic.Adds.

Fixes #1247

HC for google_https does not work because it does not HC the correct
set of IPs. Hard to solve in the current code - rather use forward as
the new impl. and leave this as legacy.

Remove superfluous println that we are refreshing the dns.google.com IP
address.

* metrics: use exponentional buckets

See  https://github.com/kubernetes/dns/pull/168

See #1211 for disuccsion; current code is probably the wrong thing to
do; rethink if we need/want this. Comment out the code for now.

* plugin/rewrite: don't set or use ecs.DraftOption

Don't know why we are accessing this and explicitally setting it to
False (the default).
Any kill with fire - makes the build, build again.

* remove this

- Dnstap require protocol, address and port info about peer. So, I
   removed conversion of TCPAddr to IPAddr

* Use seconds for bucketing.
* Add template for high accuracy timing buckets to avoid copy-pasta.

Use caching, just ask etcd for every query. This also improves
throughput because the single lock in inflght is bypassed.

* ipv6 UT for endpoint

* tweak

Remove most 303 TTLs (those get skipped by the test) and use 5, which is
the default for all tests.

The TTL was still zero, instead it should adhere to the k.ttl setting.
Change this and update tests to match.

* clean up and add some ipv6 tests

* aaaa endpoint

* gofmt

* plugin/kubernetes: Add GetNamespaceByName

A bare or wildcard query for just the namespace should return NODATA,
not NXDOMAIN, otherwise we deny the entirety of the names under the
namespace.

Add test to check for this in pod verified mode.

* Review

More comments and move namespace code to namespace.go

* Update vendor directory for latest changes.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

* Update Gopkg.toml to remove the constraint on zipkin-go-opentracing

As the issue on zipkin-go-opentracing has been fixed. See #1193
for details.
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>

super small cleanup; smaller case return errors.

Check the error returned by clientConfig.ClientConfig() before trying to
set cc.ContentType.
Signed-off-by: Andy Goldstein <andy.goldstein@gmail.com>

Add a note in about using the 'pinned' label for prevent stalebot from
closing your issue.

Implement health.Healther in erratic and kubernetes plugin. The
kubernetes' healtcheck is only performed on startup - i.e. turn
healthy after the initial loading.

Erratic follow the drop count: every query%drop turns the healthcheck
unhealthy.

Fixes: #985

* plugin/log: remove need to specify stdout

Since log will only be output to stdout is doesn't make sense to
specify it in Corefile.

Fixes: #1218

* fixup! plugin/log: remove need to specify stdout

* use index for svc reverse lookup

* temp revert

* restore reverse.go

* restore reverse_test.go

* plugin/log: remove OutputFile

We use stdout for everything, remove OutputFile as it isn't used and
causes confusion.

Fixes #1216

* PR feedback

No need to have this build all the time.

Because we have our own mux we can't depend on the dns.Mux to do the
Question section checking for us. Clarify this in the comment.

I think this badge is misleading as we are not a library so the number of projects we are used in is not really relevant to our adoption. It is more-or-less just the number of external plugins people have built.