auto content sync

content/blog/coredns-1.8.0.md

@@ -48,11 +48,16 @@ example.org {
 
 ## Brought to You By
 
+Chris O'Haver,
+Macks,
 Miek Gieben,
 Yong Tang.
 
 ## Noteworthy Changes
 
-* plugin/cache: Fix filtering (https://github.com/coredns/coredns/pull/4148)
-* plugin/transfer: Implement notifies for transfer plugin (https://github.com/coredns/coredns/pull/3972) (#4142)
+* core: doh support: make no TLS config fatal (https://github.com/coredns/coredns/pull/4162)
 * core: Move caddy v1 in our GitHub org (https://github.com/coredns/coredns/pull/4018)
+* plugin/auto: allow fallthrough if no zone match (https://github.com/coredns/coredns/pull/4166)
+* plugin/cache: Fix filtering (https://github.com/coredns/coredns/pull/4148)
+* plugin/ready: dont return 200 during shutdown (https://github.com/coredns/coredns/pull/4167)
+* plugin/transfer: Implement notifies for transfer plugin (https://github.com/coredns/coredns/pull/3972) (#4142)

content/plugins/health.md

@@ -1,10 +1,10 @@
 +++
 title = "health"
 description = "*health* enables a health check endpoint."
-weight = 21
+weight = 22
 tags = ["plugin", "health"]
 categories = ["plugin"]
-date = "2020-02-06T12:07:03.877382"
+date = "2020-10-01T15:21:54.87754810"
 +++
 
 ## Description
@@ -29,8 +29,8 @@ health [ADDRESS] {
 }
 ~~~
 
-* Where `lameduck` will make the process unhealthy then *wait* for **DURATION** before the process
-  shuts down.
+* Where `lameduck` will delay shutdown for **DURATION**. /health will still answer 200 OK.
+  Note: The *ready* plugin will not answer OK while CoreDNS is in lameduck mode prior to shutdown.
 
 If you have multiple Server Blocks, *health* can only be enabled in one of them (as it is process
 wide). If you really need multiple endpoints, you must run health endpoints on different ports: