search for: resolvd

.... I have two other servers. Once the ad-cd server is up the I plan to have the other servers moved to ad and act as alternate dcs > Louis went down the same path as you, least amount of changes, Louis however also used Bind9 in his recent notes. I'm somewhat concerned that removing systemd-resolvd will create other issues. > You pays your money and makes your choices ;-) You still have to live with them later. B-) > Rowland One question. Can I simply re-provision the server and overwrite the existing configuration if I decide to go to bind9? -- Rob Steinmetz

On 14/06/2023 12:10, Rowland Penny via samba wrote: > > > On 14/06/2023 11:48, Michael Tokarev via samba wrote: >> >> This shouldn't be a problem by its own.? On a laptop without its own >> local domain >> name it doesn't matter much which domain search to use, and "." is >> about right >> anyway. > > I totally agree, it

OK I'm back on this after a tour through firewalld and other issues. I see Louis has posted his how to on git-hub. It seems very helpful I also see his method uses the Ubuntu resolver but also uses bind9 so I'm not sure whether his method can be adapted to using the internal DNS in Samba. In setting this up one of my main goals is to limit the amount of customization I do as I have

Hai Barry, We know about exchange might be a problem, the others i dont know.. Check the windows schema levels. https://wiki.samba.org/index.php/AD_Schema_Version_Support You could try a clean setup as shown by my howto. Before you install setup ip and hostname in the windows DNS for the linux server. Make sure you use a name thats never used before, just to be sure of no side effects.

On 29/05/2023 18:31, Rowland Penny via samba wrote: > > > On 29/05/2023 14:25, Rowland Penny via samba wrote: >> >> >> On 29/05/2023 13:41, Marco Gaiarin via samba wrote: >>> Mandi! Kees van Vloten via samba >>> ?? In chel di` si favelave... >>> >>>> To me it looks identical to this >>>>

...ion details. ************ Also, since I'm stopped for now... you had me create a resolv.conf file here: /etc/systemd/resolv.conf Yet Ubuntu has it here: /etc/resolv.conf AND.... that is a "read only" file as it is dynamically updated as Ubuntu uses Netplan... I have not uninstalled resolvd as I did before under other guidance. I created the file you directed in the How-to, but I don't think it is doing anything. Never the less the is NO problem resolving to whatever valid DNS name used in nslookup. I did not want to proceed until you let me know if there is something wrong wit...

I was rereading this i missing one thing, my dislectic got me again.. In the last part. Just before all systemctl's. This : and we change the systemd-resolved and point it to the IP ( NOT localhost ) of the server now change the systemd-resolvd DNS. sed "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf The sed line should be : sed -i "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf Or sed "s/DNS=8.8.8.8/DNS=192.168.0.10/g" /etc/systemd/resolved.conf Greetz, Louis > -...

But these are online for almost a year now... ;-) https://github.com/thctlo/samba4/tree/master/howtos The only thing is these are not useing "my" builded packages but the original debians. I'll update these somewhere today or next week also with the 4.8 parts added. Basicly its, follow the howtos until you need to install samba. And just before that, run this. echo "deb

...Z > > I was rereading this i missing one thing, my dislectic got me again.. > > In the last part. > Just before all systemctl's. > This : > > and we change the systemd-resolved and point it to the IP ( > NOT localhost ) of the server > now change the systemd-resolvd DNS. > sed "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf > > The sed line should be : > sed -i "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf > Or > sed "s/DNS=8.8.8.8/DNS=192.168.0.10/g" /etc/systemd/resolved....

...interface to the systemd resolver. echo " [Match] Name=eth0 [Network] DNS=192.168.0.10 DNSSECNegativeTrustAnchors=lan Domains=lan" >> /etc/systemd/network/eth0.network and we change the systemd-resolved and point it to the IP ( NOT localhost ) of the server now change the systemd-resolvd DNS. sed "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf # Note, the DNS=$(hostname -i) that is the ip of the server. NOT 127.0.0.1. systemctl daemon-reload systemctl reload apparmor systemctl restart systemd-networkd systemctl restart systemd-resolved systemctl restar...

...'dns' entry MUST precede 'mdns4_minimal' > and 'mdns4' entries. Possible yes, but if correctly setup, not needed. And a bit ahead thinking people... Future systems, will mostly use systemd, if we like it or not. Then if systemd is use correctly and you use the systemd-resolvd, you get this. A random new server im setting up, not a samba server, but that not the point, the point is resolving, And what you see in this output. sudo resolvectl ( the defaults ) Global LLMNR setting: yes MulticastDNS setting: yes DNSOverTLS setting: no DNSSEC setting: no...

Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there):   Name=, Records=3, Children=0     SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600,