doc update (#703)

1 files changed, 13 insertions, 1 deletions

diff --git a/middleware.md b/middleware.md
index 46e6e0673..40236292f 100644
--- a/middleware.md
+++ b/middleware.md
@@ -33,7 +33,7 @@ something has been written to the client (by the middleware).
 
 See a couple of blog posts on how to write and add middleware to CoreDNS:
 
-* <https://blog.coredns.io/#> TO BE PUBLISHED.
+* <https://blog.coredns.io/2017/03/01/how-to-add-middleware-to-coredns/>
 * <https://blog.coredns.io/2016/12/19/writing-middleware-for-coredns/>, slightly older, but useful.
 
 ## Metrics
@@ -132,3 +132,15 @@ answer for the MX query:
 % dig +nocmd @localhost +noall +ans MX compute.internal
 compute.internal.	3600	IN	MX	10 mx.compute.internal.
 ~~~
+
+## Qualifying for main repo
+
+Middleware for CoreDNS can live out-of-tree, `middleware.cfg` defaults to CoreDNS' repo but other
+repos work just as well. So when do we consider the inclusion of a new middleware in the main repo?
+
+* First, the middleware should be useful for other people. "Useful" is a subjective term. We will
+  probably need to further refine this.
+* Current internet standards need be supported: IPv4 and IPv6, so A and AAAA records should be
+  handled (if your middleware is in the business of dealing with address records that is).
+* It must have tests.
+* It must have a README.md for documentation.