search for: lenkin

...> first... > > > >? ?* Netplan:? The symlink? /etc/resolv.conf to > >? ? ?/run/systemd/resolve/stub-resolv.conf was wrong.? It now goes to > >? ? ?/run/systemd/resolve/resolv.conf.? And > > > >? ? ?_admin at fsvr0:/etc$ nslookup dc0.lan.lenkin.com > <http://dc0.lan.lenkin.com> > >? ? ?<http://dc0.lan.lenkin.com>_ > > > >? ? ? ? ?Server: ? ? ? ? 10.199.251.10 > > > >? ? ? ? ?Address: ? ? ? ?10.199.251.10#53 > > > > > >? ? ? ? ?Name: dc0.lan....

...d with respect to the fileserver configs.? Good news > first... > > * Netplan:? The symlink? /etc/resolv.conf to > /run/systemd/resolve/stub-resolv.conf was wrong.? It now goes to > /run/systemd/resolve/resolv.conf.? And > > _admin at fsvr0:/etc$ nslookup dc0.lan.lenkin.com > <http://dc0.lan.lenkin.com>_ > > Server: ? ? ? ? 10.199.251.10 > > Address: ? ? ? ?10.199.251.10#53 > > > Name: dc0.lan.lenkin.com <http://dc0.lan.lenkin.com> > > Address: 10.199.251.10 > > So the command...

Following the guidance here, https://wiki.samba.org/index.php/Idmap_config_ad, I added idmap lines to my smb.conf file on my Samba 4.7 AD-DC server on Ubuntu 18.04. Samba no longer starts and testparm reports that the idmap ranges for the default * domain and the AD domain are overlapping. Here's my smb.conf file (FWIW, if I don't comment security = ADS, server role is set to Member

...m.example.com > <http://samdom.example.com>] > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? addresses: [10.199.251.10] > > #EOF > > # /run/systemd/resolve/stub-resolv.conf > > nameserver 127.0.0.53 > options edns0 > search samdom.example.com <http://lan.lenkin.com> workgroup > > #EOF That may or may not work > > # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg > > network: > ? ? config: disabled > > #EOF > > Testing DNS > > _admin at fsvr0:/$ nslookup dc0.samdom.example.com > <http://d...