aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-12-17 20:58:41 +0000
committerNick Mathewson <nickm@torproject.org>2008-12-17 20:58:41 +0000
commit43393b4b33b12e03e38da55da2ac4a38a13c4af8 (patch)
treeac1718c54be64effe80168ad54061fe24bad8775 /doc
parentd58de02778ead3282c5b04a6fa0bd8b77ce094b5 (diff)
downloadtor-43393b4b33b12e03e38da55da2ac4a38a13c4af8.tar
tor-43393b4b33b12e03e38da55da2ac4a38a13c4af8.tar.gz
manpage: stop mentioning the possibility that Tor has been built without eventdns. That hasn't been possible since 0.2.0.1-alpha
svn:r17655
Diffstat (limited to 'doc')
-rw-r--r--doc/tor.1.in15
1 files changed, 5 insertions, 10 deletions
diff --git a/doc/tor.1.in b/doc/tor.1.in
index 9924dbff2..b723110a1 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -972,8 +972,7 @@ Overrides the default DNS configuration with the configuration in
\fIfilename\fP. The file format is the same as the standard Unix
"\fBresolv.conf\fP" file (7). This option, like all other
ServerDNS options, only affects name lookups that your server does on
-behalf of clients. Also, it only takes effect if Tor was built with
-eventdns support. (Defaults to use the system DNS configuration.)
+behalf of clients. (Defaults to use the system DNS configuration.)
.LP
.TP
\fBServerDNSSearchDomains \fR\fB0\fR|\fB1\fR\fP
@@ -982,8 +981,7 @@ domain. For example, if this system is configured to believe it is in
"example.com", and a client tries to connect to "www", the client will be
connected to "www.example.com".
This option only affects name lookups that your server does on
-behalf of clients, and only takes effect if Tor was built with
-eventdns support.
+behalf of clients.
(Defaults to "0".)
.LP
.TP
@@ -993,8 +991,7 @@ our local nameservers have been configured to hijack failing DNS requests
(usually to an advertising site). If they are, we will attempt to correct
this.
This option only affects name lookups that your server does on
-behalf of clients, and only takes effect if Tor was built with
-eventdns support.
+behalf of clients.
(Defaults to "1".)
.LP
.TP
@@ -1003,8 +1000,7 @@ When we're detecting DNS hijacking, make sure that these \fIvalid\fP
addresses aren't getting redirected. If they are, then our DNS is
completely useless, and we'll reset our exit policy to "reject *:*".
This option only affects name lookups that your server does on
-behalf of clients, and only takes effect if Tor was built with
-eventdns support.
+behalf of clients.
(Defaults to "www.google.com, www.mit.edu, www.yahoo.com,
www.slashdot.org".)
.LP
@@ -1015,8 +1011,7 @@ containing illegal characters (like @ and :) rather than sending them to an
exit node to be resolved. This helps trap accidental attempts to resolve
URLs and so on.
This option only affects name lookups that your server does on
-behalf of clients, and only takes effect if Tor was built with
-eventdns support.
+behalf of clients.
(Default: 0)
.LP
.TP