Chris O'Haver

please also add this to log plugin documentation

This is a bit too cryptic. Can you ask with more detail?

From reading https://github.com/coredns/coredns/pull/4531, it seems the change was done because it was easier to disable than fix. If you'd like to propose a fix you may do so.

The [_fanout_ external plugin](https://coredns.io/explugins/fanout/) may act this way. Per the fanout README, it says that it forwards the first "non-negative" response. A NODATA response (i.e. a NOERROR with zero answers)...

> worker count should be more or equal 2. That's unfortunate. Should be an easy fix though. I suspect the 2 minimum is as arbitrary as it is undocumented. >...

> For some reason, this is also not being tagged as the latest release when you go to the releases page. This because 1.11.3 is not fully released. The docker...

Done. 1.11.3 now marked pre-release.

When I get some time, I'll enable actions in my fork and do a release to my personal docker account. This should identify if the issue is with the build...

@heiko-braun, I had some time a last week to try to work out migrating to docker build/push actions to enable publishing images to both docker and github's container repo. I...

If a maintainer with admin permissions in the coredns dockerhub org could generate a token and then update the coredns/coredns secrets: DOCKERHUB_USERNAME (to yours) and DOCKERHUB_PASSWORD (to be your token...