From: Sam P. <sa...@ar...> - 2004-08-11 18:54:57
|
Le mar 10/08/2004 =E0 23:14, Carl Wilhelm Soderstrom a =E9crit : > On 08/10 11:09 , Sam Przyswa wrote: > > I noticed after the command "/usr/share/BackupPC/bin/BackupPC_dump -v= -f > > hostname" the command "dig mars.dyn.ac-fr.com" don't work anymore, th= e > > resolver go down. >=20 > if the host itself can't resolve the name; you have problems outside of > BackupPC. :( BackupPC doesn't affect anything on the system itself; so = I > think you have more endemic problems. :( The problem is very strange, my BackupPC machine is on a LAN behind a Firewall/ADSL Gateway/DNS as 172.16.0.20. On my BackupPC machine my resolve.conf have "nameserver 172.16.0.20" and my machine work fine since over 3 years, I ping, ssh, apt-get, dig, all reachable machines on Internet... As soon I launch "/usr/share/BackupPC/bin/BackupPC_dump -v -f mars.dyn.ac-fr.com" : cmdSystemOrEval: about to system /bin/ping -c 1 mars.dyn.ac-fr.com cmdSystemOrEval: finished: got output ping: unknown host mars.dyn.ac-fr.com Then I can't resolve any hostname anymore, "dig mars.dyn.ac-fr.com" return nothing. The only thing that's fix is to ADD a public nameserver outside my LAN in to resolve.conf on my BackupPC machine. Then everything works fine. I'm not sure that this problem is 100% endemic and I think BackupPC or Perl have something to deal with but I don't know what. I think you have to look this problem (BackupPC developers) I'm sure other users will have the same problem someday. I hope this help... Thanks to Carl and all others on this list. Sam. |