[Samba] replication fails

Stefan G. Weichinger
Wed, 13 Mar 2019 11:28:08 -0000

Am 13.03.19 um 11:55 schrieb L.P.H. van Belle via samba:
> Hai,
>
> Ok, so the reboot changed your resolv.conf
> check the timestamp of /etc/resolv.confs
> Write this down.
>
>> So I assume it should point to the own IPv4-IP of DC1 itself,
>> which is .205
> Yes correct.
> After that reboot the server.
> Check the timestamp again and/or did it change?
>
> Now the hunt for the resolv.conf change.
>
> cat /etc/network/interfaces
> If you have dns-nameserver these are picked up with systemd-resolved.
> Or by package: resolvconf
>
> Run these:
> networkctl status
> systemd-resolve --status
>
> Show the output.
>
> Other options:
> Server with dhcp ip?
> echo 'make_resolv_conf() { :; }' >
/etc/dhcp/dhclient-enter-hooks.d/leave_my_resolv_conf_alone
> chmod 755 /etc/dhcp/dhclient-enter-hooks.d/leave_my_resolv_conf_alone
>
> Or edit /etc/dhcp/dhclient.conf
> supersede domain-name "example.com";
> supersede domain-search "example.com";
> supersede domain-name-servers 127.0.0.1;
>
>
> One of above is your fix. ;-)
> A last resort fix is :
> rm -f /etc/resolv.conf
> editor /etc/resolv.conf
> chattr +i /etc/resolv.conf
>
> But i dont like that, its up2you.

I have a specific idea where that comes from and stopped/disabled
systemd-resolved now.

No DHCP.

manual replicate seems to time out (no error, no success ...)

I reboot DC2 now for a test.

Should /etc/hosts contain pointers to own FQDN or not? To DCs?

thanks