Bruno Friedmann wrote:
> On 01/04/2011 06:35 PM, pgf wrote:
> services that can be a killer in the case of change
> avahi-dns
> &
> nscd (there's actually two daemon with that name and unscd is worst that the
> old nscd )
>
It was done - in fact, the system havi
Guy wrote:
> In your conf file are you using fully qualified host names? Ie
> host.newdomain or just hostname?
>
Dan, thanks for the hint. I had one entry in bacula-dir.conf that was not fully
qualified. Just what was caching the old domain name is still unclear, but only
Bacula seemed to b
Jari Fredriksson wrote:
> On 3.1.2011 21:21, pgf wrote:
> Have you tried telnet to the port? I was amazed that it did not work, as
>
telnet to fs1.old.domain will (and should) most definitely fail - that it the
old FQDN. The problem is not reachability; the problem is that bacula is
Jari Fredriksson wrote:
> On 3.1.2011 18:06, pgf wrote:
> I don't know why, but some /etc/nsswitch.conf with these lines
>
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
>
> fails for me in this situation.
>
> hosts: files dns
>
&
After a a domain name change of my entire network I am getting an error from
Bacula. For some reason it is still trying to look up the hosts by their old
domain name:
Error: bsock.c:208 gethostbyname() for host "fs1.old.domain"
failed: ERR=Authoritative answer for host not found.
I have verifi
