HI there

I have an issue where BackupPC can't backup some hosts anymore. Let me
explain

  * I backup a bunch of servers behind bastion hosts. SSH tunneling is
    configured in ~backuppc/.ssh/config
  * Some of the host behind the bastion do not have a corresponding
    public DNS entry published
  * For all of my hosts, the name of the machine is meaningless. It's
    something like client1_machine3. The DNS name is always set in the
    ClientNameAlias
  * For host behind a bastion, I change the PingCmd to $pingPath -c 1 -w
    3 bastion.host.net so the bastion is pingued and its latency can be
    checked

Until now, I had a wildcard DNS CNAME entry for the domain of my backup
servers, which made everything working. But as I'm changing the backend,
and don't want a wildcard (* IN CNAME foo.bar) entry, I'm now facing the
issue that, hosts behind a bastion, without a corresponding DNS entry
won't backup anymore. The error is


2018-11-23 08:59:53 Can't find host ldap.client1.fr via NS and netbios
2018-11-23 08:59:53 can't ping  (client = client1_ldap); exiting


Of course it can't find it, and it doesn't need to because everything
will be done through an ssh tunnel, defined in .ssh/config.
With my previous setup, it would have looked for ldap.client1.fr, and
wouldn't have an anwser, and then, it would have looked for
ldap.client1.fr.firewall-services.com which would get caught by the
wildcard entry, and then, the backup could run. But the DNS answer
itself was meaningless, and not used at all.

Is there a way to disable this lookup for such cases ?

Regards, Daniel


-- 

Logo FWS

        *Daniel Berteaud*

FIREWALL-SERVICES SAS.
Société de Services en Logiciels Libres
Tel : 05 56 64 15 32
Matrix: @dani:fws.fr
/www.firewall-services.com/

_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to