similar to: Dynamic DNS Updates marked as static

Hello you all, with the new samba version out that fixes some problems with dns scavenging I have decided to try this feature. I was specifically interested for our reverse zone (PTR records) We have one zone for VPN clients 8.0.10.in-addr.arpa. I activated the feature in the smb.conf as well as in the Windows DNS manager. Entries are deleted (not visible in DNS manager) after a while. You can

Am 18.03.20 um 22:26 schrieb Andrew Bartlett: >> Also "samba-tool domain tombstones expunge --tombstone-lifetime=0" >> does >> not delete the records with "dNSTombstoned: TRUE". Is this a >> different >> tombstone? > > That would be a different tombstone, yes. Can someone help me out with the ldap/ldb syntax to delte those by cron? >

Hello Lois, thanks for looking into this. Have you looked at what the original poster shared in the bug report? https://bugzilla.samba.org/show_bug.cgi?id=14268 I don't have a big problem with this, just trying to help. Maybe the original poster can say more with regards of the problem he has with this. here are more of my details. Regards #####samba-debug-info.txt##############

Am 16.04.20 um 14:18 schrieb Rowland penny via samba: > On 16/04/2020 12:45, Christian Naumer via samba wrote: >> Hello alAl, >> after update of our test server to 4.12.1 from 4.11 it crashes. If the >> vfs module is removed from the config everthing works as before. > > The only change was to upgrade to 4.12.1 ? > > If there were no other changes, then Samba

What version of Samba is this and do you have "server schannel = no" set in its smb.conf? Regards Christian Am 09.11.20 um 15:31 schrieb Andrea Cucciarre' via samba: > The DC is a Windows AD DC. > Could you please clarify why i should change setting in the Windows DC > instead of the Samba server, which is the one that does the insecure > ldap bind? > >

Am 17.11.20 um 13:20 schrieb mj via samba: >> ,--- >> CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=samba,DC=company,DC=com >> >> >> |,-- >>

Am 26.02.20 um 15:40 schrieb L.P.H. van Belle via samba: > So strange.. > > I copied your commando's only change the arpa and servername / domainnames > All worked. Have you checked that you have this situation? If this entry "192.168.2.157" exists and if you try to add "192.168.0.157" another entry to point to "192.168.2.157" is added. >

Am 16.04.20 um 14:23 schrieb Christian Naumer via samba: > Am 16.04.20 um 14:18 schrieb Rowland penny via samba: >> On 16/04/2020 12:45, Christian Naumer via samba wrote: >>> Hello alAl, >>> after update of our test server to 4.12.1 from 4.11 it crashes. If the >>> vfs module is removed from the config everthing works as before. >> >> The only change

Hello All, now that the BUG 14343: (s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[] array.) was fixed I wanted to try 4.12 again. This is the relevant config which has been running for years: vfs objects = acl_xattr full_audit shadow_copy2 full_audit:failure = none full_audit:success = pwrite write rename unlink full_audit:prefix = IP=%I|USER=%u|MACHINE=%m|VOLUME=%S

Am 24.07.20 um 14:51 schrieb Rowland penny via samba: > > NFS shares != Samba shares and 'mounting' != hosting Samba shares ;-) > > Up until Samba 4.8.0, 'smbd' (the fileserver component on a Unix domain > member) could contact AD directly, but after 4.8.0 , smbd must now go > through winbind, sssd uses some of the winbind code, so it is > incompatible with

How about the one from the Samba Wiki. https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member It is not a walk through but it covers the important points. Regards > Am 06.09.2020 um 01:34 schrieb Peter Pollock via samba <samba at lists.samba.org>: > > ?I have a domain with two Samba DC's > > I don't want to use either of them as a fileserver, so

Am 24.09.20 um 13:29 schrieb Robert Wooden via samba: > I have some (for testing) Debian based client/workstation connected to my > AD. Signing to the AD works as a domain/user should. These clients can, via > Nautilus file manager, access shares on the file server manually that > the *signed > in domain user* is permitted to "see". I would prefer to connect these >

On 02.10.20 14:27, Rowland penny via samba wrote: > I read that, about as much use as a chocolate fireguard if you want to > use winbind. pam_sss (or whatever it is called) is just a wrapper around > sssd and you cannot usee sssd with winbind, Red-Hat tells you this! Hi Rowland, this was true for Centos7 but for 8 it works fine without pam_krb5. If you have access you can see this

Am 20.10.20 um 19:36 schrieb Rowland penny via samba: > On 20/10/2020 17:46, Stefano Vargiu wrote: >> Sorry, I don't get it. >> >> You?mean a domain member as opposed to a domain controller? >> In which way is it?going?to help? >> > You should really only use a Samba AD DC for authentication, so the best > idea would be to add a Unix domain member to the

Am 24.07.20 um 12:57 schrieb Jason Keltz via samba: > > The reason in particular that I was looking at sssd client as opposed to winbind was that? we are running CentOS 7. I know if I want to use the latest Samba 4.12 on the clients, I'll have problems with gnutls because it's outdated in CentOS 7.? Yes, someone has figured out a way around that by compiling a separate gnutls, but

Do you have something like this in your smb.conf? dns forwarder = 8.8.8.8 Regards > Am 05.09.2020 um 23:39 schrieb Peter Pollock via samba <samba at lists.samba.org>: > > ?..and also, kinit fails if I don't have 192.168.4.5 as the first nameserver > in resolv.conf > >> On Sat, Sep 5, 2020 at 10:26 AM Rowland penny via samba < >> samba at

Hello all, I just tried this on our setup and it ist the same there. I get results from other OUs. Using sub instead of one I get the "right" results. Regards Christian Am 01.02.20 um 20:26 schrieb Andrew Bartlett via samba: > On Sat, 2020-02-01 at 17:22 +0000, Rowland penny via samba wrote: >> On 01/02/2020 16:29, Palle Kuling via samba wrote: >>> >>>

Hai, Today i thought lets re-test this again. So this was done yesterday, samba-tool dns add dc1.internal.dom.tld 2.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld samba-tool dns add dc1.internal.dom.tld 0.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld samba-tool dns add dc1.internal.dom.tld 1.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld I did keep the entries in the dns

> Am 15.03.2020 um 08:21 schrieb S?rgio Basto via samba <samba at lists.samba.org>: > > ?On Sat, 2020-03-14 at 07:43 -0700, gabben via samba wrote: >> Your pfSense firewall has OpenVPN built into it already, and you can >> point pfSense authentication back to your samba AD. We support over >> 400 users in this model. The configuration file for OpenVPN is common

Must be something with/or in combination with Centos and/or sernet packages. I just tested : samba-tool dns add dc1.internal.dom.tld 2.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld samba-tool dns add dc1.internal.dom.tld 0.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld samba-tool dns add dc1.internal.dom.tld 1.249.10.in-addr.arpa 157 PTR host.extrazone.dom.tld All checks are fine