summaryrefslogtreecommitdiff
path: root/network/ttdnsd
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 03:28:57 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-14 03:28:57 -0400
commitce3e7ad590249eed1066571e8d13b8d242c9c1ee (patch)
tree803703a96f651e8a30cff53637733b95f6f4572a /network/ttdnsd
parent7fe85953d2a40758dac512a86cffbb42adc4f170 (diff)
downloadslackbuilds-ce3e7ad590249eed1066571e8d13b8d242c9c1ee.tar.gz
network/ttdnsd: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'network/ttdnsd')
-rw-r--r--network/ttdnsd/README41
1 files changed, 23 insertions, 18 deletions
diff --git a/network/ttdnsd/README b/network/ttdnsd/README
index 2f24e6238c..cc9a454851 100644
--- a/network/ttdnsd/README
+++ b/network/ttdnsd/README
@@ -1,30 +1,35 @@
-ttdnsd accepts DNS requests via UDP and forwards the to a resolving nameserver
-via TCP. The actual requests are really just forwarded so one has complete
-access to the nameserver ttdnsd is talking to. -- It's not a very complicated
-process. If there are no problems with the setup it could go as smoothly as
-connecting to the 'net using a mobile broadband dongle.
+ttdnsd accepts DNS requests via UDP and forwards the to a resolving
+nameserver via TCP. The actual requests are really just forwarded so
+one has complete access to the nameserver ttdnsd is talking to.
-ttdnsd only connects to the resolving nameserver after receiving a request via
-UDP. For each connection ttdnsd randomly selects one of the nameservers it
-knows about. The connection will be used for forwarding multiple requests in a
-pipelined fashion and is kept open only until no more requests are received
-via UDP. This pipelining is required to overcome the initial connection
-overhead time which is quite long when using Tor.
+It's not a very complicated process. If there are no problems with the
+setup it could go as smoothly as connecting to the 'net using a mobile
+broadband dongle.
-To run this service at system startup, edit your rc.local and add this code:
+ttdnsd only connects to the resolving nameserver after receiving
+a request via UDP. For each connection ttdnsd randomly selects one
+of the nameservers it knows about. The connection will be used for
+forwarding multiple requests in a pipelined fashion and is kept open
+only until no more requests are received via UDP. This pipelining is
+required to overcome the initial connection overhead time which is
+quite long when using Tor.
+
+To run this service at system startup, edit your rc.local and add this
+code:
if [ -x /etc/rc.d/rc.ttdsnd ]; then
/etc/rc.d/rc.ttdsnd start
fi
-after the similar code used to start the Tor service. To stop the service add
-this to your rc.local_shutdown:
+...after the similar code used to start the Tor service. To stop the
+service add this to your rc.local_shutdown:
if [ -x /etc/rc.d/rc.ttdsnd ]; then
/etc/rc.d/rc.ttdsnd stop
fi
-before the Tor shutdown routines. Remember that this package acts like a DNS
-resolver so it listens by default on port 53. If you're going to run another
-DNS server like bind either as a cache to this server or in parallel, remember
-to modify ttdnsd default port or it will not start.
+...before the Tor shutdown routines. Remember that this package acts
+like a DNS resolver so it listens by default on port 53. If you're
+going to run another DNS server like bind either as a cache to this
+server or in parallel, remember to modify ttdnsd default port or it
+will not start.