Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-12-21 17:45:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

doc update (#703)

Browse Source
This commit is contained in:
Miek Gieben
2017-06-03 08:26:51 +01:00
committed by GitHub
parent ecae087201
commit 6d52827a8a
2 changed files with 22 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
middleware.md
View File

@@ -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.