Package: pdnsd Version: 1.2.4par-0.2 Arch: i386 Greetings-
This bug against pdnsd is a simple misconfiguration problem and the fixes are an even bigger problem. The reason pdnsd does not start when the init.d script is called by the install script is shown to be the named already using port 53. That is the correct behavior. The pdnsd.conf file needs to be customized before the pdnsd can run anyway. The install script should not fail because pdnsd does not start. That is the incorrect behavior. I have bind9 and pdnsd installed and they were both working fine together until the NMU patch. Now pdnsd does not start when configured to use 127.0.0.2:53 because named is already running on 127.0.0.1:53. That is the fault of the NMU diff patch. The NMU diff is the wrong way to solve a problem with the install script. I am now working around the problem. The pdnsd and named are supposed to work together while both programs are running at the same time. The NMU diff ruins that cooperation and pdnsd should be reverted. If the install script is the problem then fix that script. Just issue a message to configure pdnsd for the actual system before running the init.d script. Don't even try to run the init.d script during installation. -Captain
