From b532b13dd9ee91a52577f24deb6ce157ec6ba7a6 Mon Sep 17 00:00:00 2001 From: Ruben Kerkhof Date: Mon, 29 Sep 2014 20:46:57 +0200 Subject: [PATCH] Convert dnsdist.1.txt to Unix LF --- pdns/docs/dnsdist.1.txt | 96 ++++++++++++++++++++--------------------- 1 file changed, 48 insertions(+), 48 deletions(-) diff --git a/pdns/docs/dnsdist.1.txt b/pdns/docs/dnsdist.1.txt index bd04916473..c175743f1f 100644 --- a/pdns/docs/dnsdist.1.txt +++ b/pdns/docs/dnsdist.1.txt @@ -1,68 +1,68 @@ -DNSDIST(1) +DNSDIST(1) ========== powerdns.documentation@powerdns.com NAME ---- -dnsdist - tool to balance DNS queries over downstream servers +dnsdist - tool to balance DNS queries over downstream servers SYNOPSIS -------- -'dnsdist' [--help] [--verbose] [--local address] downstream-address downstream-address - +'dnsdist' [--help] [--verbose] [--local address] downstream-address downstream-address + DESCRIPTION ----------- -dnsdist receives DNS queries and relays them to one or more downstream -servers. It subsequently sends back responses to the original requestor. - -dnsdist operates over TCP and UDP, and strives to deliver very high -performance over both. - -Currently, queries are sent to the downstream server with the least -outstanding queries. This effectively implies load balancing, making sure -that slower servers get less queries. - -If a reply has not come in after a few seconds, it is removed from the -queue, but in the short term, timeouts do cause a server to get less -traffic. - -IPv4 and IPv6 operation can be mixed and matched, in other words, queries -coming in over IPv6 could be forwarded to IPv4 and vice versa. - -SCOPE ------ -dnsdist does not 'think' about DNS, and does not perform any kind of -caching, nor is it aware of the quality of the answers it is relaying. - -dnsdist assumes that each query leads to exactly one response, which is true -for all DNS except for AXFR, which is therefore not supported. - -The goal for dnsdist is to remain simple. If more powerful loadbalancing is -required, dedicated hardware or software is recommended. Linux Virtual -Server for example is often mentioned. - +dnsdist receives DNS queries and relays them to one or more downstream +servers. It subsequently sends back responses to the original requestor. + +dnsdist operates over TCP and UDP, and strives to deliver very high +performance over both. + +Currently, queries are sent to the downstream server with the least +outstanding queries. This effectively implies load balancing, making sure +that slower servers get less queries. + +If a reply has not come in after a few seconds, it is removed from the +queue, but in the short term, timeouts do cause a server to get less +traffic. + +IPv4 and IPv6 operation can be mixed and matched, in other words, queries +coming in over IPv6 could be forwarded to IPv4 and vice versa. + +SCOPE +----- +dnsdist does not 'think' about DNS, and does not perform any kind of +caching, nor is it aware of the quality of the answers it is relaying. + +dnsdist assumes that each query leads to exactly one response, which is true +for all DNS except for AXFR, which is therefore not supported. + +The goal for dnsdist is to remain simple. If more powerful loadbalancing is +required, dedicated hardware or software is recommended. Linux Virtual +Server for example is often mentioned. + OPTIONS ------- --verbose:: Be wordy on what the program is doing - ---local:: - Supply as many addresses to listen on as required. Specify IPv4 as - 0.0.0.0:53 and IPv6 as [::]:53. - ---daemon:: - Daemonize and run in the background - ---help:: - Provide a helpful message - -Finally, supply as many downstream addresses as required. Remote port defaults to 53. - + +--local:: + Supply as many addresses to listen on as required. Specify IPv4 as + 0.0.0.0:53 and IPv6 as [::]:53. + +--daemon:: + Daemonize and run in the background + +--help:: + Provide a helpful message + +Finally, supply as many downstream addresses as required. Remote port defaults to 53. + BUGS ---- -Right now, the TCP support has some rather arbitrary limits. - +Right now, the TCP support has some rather arbitrary limits. + AUTHOR ------ Written by PowerDNS.COM BV, powerdns.documentation@powerdns.com -- 2.47.2