From 1b64a75e6f9c57fc15c61d511e614502ec0be5b6 Mon Sep 17 00:00:00 2001 From: Christian Hofstaedtler Date: Thu, 25 Dec 2014 17:25:34 +0100 Subject: [PATCH] docs: Remove PING from pipebackend PING is never sent by pipebackend, so don't have it in the docs. --- docs/markdown/authoritative/backend-pipe.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/markdown/authoritative/backend-pipe.md b/docs/markdown/authoritative/backend-pipe.md index 893f3d05f..7fc8c3615 100644 --- a/docs/markdown/authoritative/backend-pipe.md +++ b/docs/markdown/authoritative/backend-pipe.md @@ -70,12 +70,7 @@ Questions come in over a file descriptor, by default standard input. Answers are ## Handshake PowerDNS sends out `HELO\t1`, indicating that it wants to speak the protocol as defined in this document, version 1. For abi-version 2 or 3, PowerDNS sends `HELO\t2` or `HELO\t3`. A PowerDNS Coprocess must then send out a banner, prefixed by `OK\t`, indicating it launched successfully. If it does not support the indicated version, it should respond with `FAIL`, but not exit. Suggested behaviour is to try and read a further line, and wait to be terminated. -### Questions -Questions come in three forms and are prefixed by a tag indicating the type: - -* `Q`: Regular queries -* `AXFR`: List requests, which mean that an entire zone should be listed -* `PING`: Check if the coprocess is functioning +### `Q`: Regular queries for data The question format, for type Q questions: @@ -102,6 +97,8 @@ Type is the tag above, `qname` is the domain the question is about. `qclass` is **Note**: Queries for wildcard names should be answered literally, without expansion. So, if a backend gets a question for "*.powerdns.com", it should only answer with data if there is an actual "*.powerdns.com" name +### `AXFR`: List an entire zone + AXFR-queries look like this: ``` -- 2.40.0