The init script for proftpd should include use dns to ensure that proftpd is started after named on hosts that are their own DNS resolver. Proftpd attempts to do a look up on its configured hostname at startup and will fail if the dns server has not been started first. The command sequence below illustrates this problem. If the system worked as expected, named would have been started automatically for me when I attempted to start proftpd. adam@tweety /etc/init.d $ sudo /etc/init.d/named stop * Stopping named ... [ ok ] adam@tweety /etc/init.d $ sudo /etc/init.d/proftpd start * Starting proftpd ... - IPv4 getaddrinfo 'tweety.bump.us' error: Temporary failure in name resolution - warning: unable to determine IP address of 'tweety.bump.us' - error: no valid servers configured - Fatal: error processing configuration file '/etc/proftpd/proftpd.conf [ !! ] adam@tweety /etc/init.d $ sudo /etc/init.d/named start * Starting named ... [ ok ] adam@tweety /etc/init.d $ sudo /etc/init.d/proftpd start * Starting proftpd ... [ ok ] Here is a similar command sequence once I have included 'use dns' in the depend section of /etc/init.d/proftpd: adam@tweety /etc/init.d $ sudo /etc/init.d/named stop * Stopping named ... [ ok ] adam@tweety /etc/init.d $ sudo /etc/init.d/proftpd start * Starting named ... [ ok ] * Starting proftpd ... [ ok ]
Fixed in net-ftp/proftpd-1.3.0-r2. Thanks for the fix! Best regards, CHTEKK.
