From: bert hubert Date: Wed, 28 Oct 2015 20:34:39 +0000 (+0100) Subject: add link to blogpost to clarify what backends are X-Git-Tag: dnsdist-1.0.0-alpha1~274 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b4b9a5307e2714184e2d42a283bef1175fc923c6;p=pdns add link to blogpost to clarify what backends are --- diff --git a/docs/markdown/appendix/backend-writers-guide.md b/docs/markdown/appendix/backend-writers-guide.md index c8254ad8b..e3e186e16 100644 --- a/docs/markdown/appendix/backend-writers-guide.md +++ b/docs/markdown/appendix/backend-writers-guide.md @@ -1,5 +1,11 @@ # Backend writers' guide -PDNS backends are implemented via a simple yet powerful C++ interface. If your needs are not met by the PipeBackend, you may want to write your own. Before doing any PowerDNS development, please visit [the wiki](http://wiki.powerdns.com). + +PowerDNS backends are implemented via a simple yet powerful C++ interface. +If your needs are not met by the PipeBackend, you may want to write your +own. Before doing any PowerDNS development, please visit [the +wiki](http://wiki.powerdns.com). Also please read [this blog +post](http://blog.powerdns.com/2015/06/23/what-is-a-powerdns-backend-and-how-do-i-make-it-send-an-nxdomain/) +which has a FAQ and several pictures that help explain what a backend is. A backend contains zero DNS logic. It need not look for CNAMEs, it need not return NS records unless explicitly asked for, etcetera. All DNS logic is contained within PDNS itself - backends should simply return records matching the description asked for.