search for: samba_dnsudp

Hello, Has anyone already installed samba4 as DC at aws? If so, how have dealt with the question of the private ip and the public ip? I will launch an instance and join samba DC to our existing active directory to work as an external authenticator for the moodle we have in the cloud. -- Elias Pereira

...t; > > > I will launch an instance and join samba DC to our existing active > > directory to work as an external authenticator for the moodle we have in > > the cloud. > > I wouldn't want Samba on a public IP ever, but if your networking > requires you you can tell samba_dnsudpate of your public IP. It has an > option to override the detected IP address. > > Perhaps try a VPN first? > > Andrew Bartlett > > -- > Andrew Bartlett http://samba.org/~abartlet/ > Authentication Developer, Samba Team http://samba.org > Samba D...

...with 'samba-tool domain provision DC'; and then joined dc34 as a DC with 'samba-tool domain join DC'. Once again, the new domain on dc33 seems to be correct and functional. However, once again, the necessary DNS records are not created for dc34 when it joins the domain. It seems samba_dnsudpate still does not work, even with the updated name resolver config. Here is an abbreviated snippet of the output from the command line on dc34, after the domain join: ------------------------------------------------------------------------ dc34:~# samba_dnsupdate --verbose IPs: ['10.150.10.3...

On 19/05/2023 03:57, Steven Monai via samba wrote: > Thanks for your reply. > > On 2023-05-18 12:29 a.m., Rowland Penny via samba wrote: > >> On 18/05/2023 04:31, Steven Monai via samba wrote: > >>> Successfully obtained Kerberos ticket to DNS/dc33.ttwo.ad.example.org >>> as DC34$ >> >> That's one misconfiguration you probably have there,

...r dc34 > when it joins the domain. When you provision a domain, most, if not all, of the required dns records are created. When you join another DC, only a few are created, the rest are created by samba_dnsupdate when Samba first starts, or that is how it is supposed to work. > It seems samba_dnsudpate still does not work, > even with the updated name resolver config. Problem is, it works for myself, I am still on bullseye, using Samba from backports, so have the same Samba version as you 4.17.8 . What is different is the version of nsupdate, mine comes from bind9-dnsutils 9.16.37, you...