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
On Wed, 13 Mar 2019 12:28:08 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote:> 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? >/etc/hosts should contain a line that points 127.0.0.1 to localhost and a line that points the DC's ipaddress to its FQDN and shorthostname EXAMPLE: 127.0.0.1 localhost 192.168.0.6 dc4.samdom.example.com dc4 There will probably be ipv6 lines as well, anything else isn't really needed, but I suppose you could add any other DC's info. Rowland
Am 13.03.19 um 12:49 schrieb Rowland Penny via samba:>> Should /etc/hosts contain pointers to own FQDN or not? To DCs? >> > > /etc/hosts should contain a line that points 127.0.0.1 to localhost and > a line that points the DC's ipaddress to its FQDN and shorthostname > > EXAMPLE: > > 127.0.0.1 localhost > 192.168.0.6 dc4.samdom.example.com dc4 > > There will probably be ipv6 lines as well, anything else isn't really > needed, but I suppose you could add any other DC's info.Thank you. The clearer the better (or so). DC2 is set up like that, but still ~500 replication failures. Off for some food and water now ... I hope I get it later. thanks all