From: TJ S. <cas...@us...> - 2010-01-05 17:01:13
|
Update of /cvsroot/pdd/www.proftpd.org/docs/howto In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv30637 Modified Files: DNS.html Log Message: Updating website copy of DNS howto. Index: DNS.html =================================================================== RCS file: /cvsroot/pdd/www.proftpd.org/docs/howto/DNS.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -r1.1 -r1.2 *** DNS.html 17 Aug 2007 00:11:26 -0000 1.1 --- DNS.html 5 Jan 2010 17:00:57 -0000 1.2 *************** *** 132,135 **** --- 132,163 ---- to re-parse its configuration and thus re-resolve all IP addresses. + <p><a name="DNSNoDNS"> + <font color=red>Question</font>: What if I do not <i>want</i> + <code>proftpd</code> to use DNS to resolve the hostname to an IP address + because I am in an environment where there is no DNS at all?<br> + <font color=blue>Answer</font>: In ProFTPD 1.3.3rc1, support for a new + <code>-S</code> command-line option was added. This option can be used to + specify the IP address of the host machine. By default, + <code>proftpd</code> attempts to resolve the host IP address by using DNS + resolution of the hostname. However, in cases where DNS is not configured for + the host machine, this approach does not work. + + <p> + To specify the desired IP address, use <code>-S</code> when starting + <code>proftpd</code>, <i>e.g.</i>: + <pre> + /usr/local/sbin/proftpd -S 1.2.3.4 ... + </pre> + And if you want <code>proftpd</code> to listen on all interfaces, you can + specify a wildcard socket using an IP address of 0.0.0.0: + <pre> + /usr/local/sbin/proftpd -S 0.0.0.0 ... + </pre> + + <p> + Note that will also mean that, in your <code>proftpd.conf</code>, any + <code><VirtualHost></code> sections will need to use IP addresses, + not DNS names. + <p> <hr> |