diff options
author | 2018-02-26 14:51:40 +0000 | |
---|---|---|
committer | 2018-02-26 14:51:40 +0000 | |
commit | d9958abc03bfe1046f90159c0f14133bb443737d (patch) | |
tree | 0064470344e3f9f60e0201f0f350a8b353fcfd02 /plugin.md | |
parent | fc6559df4bf7aa7e66e5c924e75fe508dd163774 (diff) | |
download | coredns-d9958abc03bfe1046f90159c0f14133bb443737d.tar.gz coredns-d9958abc03bfe1046f90159c0f14133bb443737d.tar.zst coredns-d9958abc03bfe1046f90159c0f14133bb443737d.zip |
doc updates (#1563)
Capatilize coredns in ADAPTERS.md
Diffstat (limited to 'plugin.md')
-rw-r--r-- | plugin.md | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -8,9 +8,9 @@ The main method that gets called is `ServeDNS`. It has three parameters: * `dns.ResponseWriter` that is, basically, the client's connection; * `*dns.Msg` the request from the client. -`ServeDNS` returns two values, a response code and an error. If the error is not nil CoreDNS -will return a generic SERVFAIL to the client. The response code tells CoreDNS if a reply has been -written by the plugin chain or not. In the latter case CoreDNS will take care of that. +`ServeDNS` returns two values, a response code and an error. If the error is not nil CoreDNS, +will return a SERVFAIL to the client. The response code tells CoreDNS if a *reply has been +written by the plugin chain or not*. In the latter case CoreDNS will take care of that. CoreDNS treats: @@ -23,7 +23,8 @@ as special and will then assume *nothing* has been written to the client. In all assumes something has been written to the client (by the plugin). The [*example*](https://github.com/coredns/example) plugin shows a bare-bones implementation that -can be used as a starting point for your plugin. +can be used as a starting point for your plugin. This plugin has tests and extensive comments in the +code. ## Hooking It Up |