similar to: PTR Records in AD

Dear all, somehow, new PTR records are not visible. This is on 4.11.6 DC with BIND9 ... Here is what happens: root at dc1:~# cat /etc/samba/smb.conf # Global parameters [global] bind interfaces only = Yes interfaces = 127.0.0.1 XXX.YYY.103.1 netbios name = DC1 realm = SAMDOM.REST_OF_FQDN server role = active directory domain controller server

So strange.. I copied your commando's only change the arpa and servername / domainnames All worked. So far nobody told how there ad-dc and DNS is setup.. Which i why i added : > > Debian 10, my own packages. > > Samba 4.11.6 + BIND9_DLZ is used . Now are you using samba DNS or BIND_DLZ dns ? That might help here. Greetz, Louis > -----Oorspronkelijk

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

Hi, I am trying to implement bitlocker key management in samba4 ad. This has been posted a view times before: https://lists.samba.org/archive/samba/2015-December/196771.html https://lists.samba.org/archive/samba/2018-July/217168.html According to Andrew and this: https://docs.microsoft.com/en-us/previous-versions/orphan-topics/ws.10/cc722309(v=ws.10) the Schema should be ready for this.

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

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? >

Hi Christian, normally I never do a reverse lookup for clients only for server and then the reverse lookup is static. If a customer want's it I do it this way: https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9 Stefan Am 03.07.19 um 11:41 schrieb Christian Naumer via samba: > Hello you all, > I have a general question. How do you guys handle the PTR

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

Hello Cristian, Well, nothing to say about your steps, these looks good. And lmdb could be disable in the sernet packages, cant say, i dont know. And only one DC has these problems or all? If only one DC crashed. Which DC crashes. Last added? Oldest? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian

Hello everybody, last weeks I started upgrading our DC from Centos 7 to Centos 8. After having read this (https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC#Updating_Multiple_Samba_Domain_Controllers) and especially this "Joining a DC to domain can be a troublesome process for some users, and it can be difficult to recover your DC if something goes wrong". I really looked forward

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. >

In addition to Rowland comment. if you still able to test it. Remove 1 setting at a time, restart and test it. Start with these, in this order. logging = syslog only prefork children = 8 I think if the logging line is removed your problem is solved. man smb.conf /logging should explain more. Because I cant/find the setting : logging = syslog only Greetz, Louis

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##############

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

I've now changed the ownership to root, as you suggest. I've removed the ACLs from /shares/DOMAIN - they don't need to be there as anyone can enter this directory already so there's no need for them. The ACLs on my individual home directory: root at server:/shares# getfacl /shares/DOMAIN/username getfacl: Removing leading '/' from absolute path names # file:

Hai, It does not happen often but yes, i also need some help as i cant know everything also and im new with freeradius. Im working on a configuration for samba member + freeradius with ntlm_auth. Why ntlm_auth, because the next one is kerberos and ldap auth to configure.. I want to have some fallback options here and you have to start somewhere. This is running on my new proxy/gateway

Hello all, after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in our logfiles: 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 20:40:44.886615, 1] ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY There are no symptoms accept

Hello you all, this is a bit OT but I think I'll find some people here that can help. We have 4 DCs all on the same site. This is working fine. 3 Are VMs one is a physical server. They are the only DNS servers in that network. On a member server running our icinga2 installation I have this in the resolv.conf: options rotate timeout:2 retries:1 search example.com nameserver x.x.x.x (ip dc1)

Am 20.05.19 um 11:59 schrieb Rowland penny via samba: >>          logging =syslog only > > Why do you have a parameter with another parameter as its value ? > > both 'logging' and 'syslog only' are both parameters, did you mean > 'logging = syslog' ? Yes I meant this "logging = syslog" > >>          server role = active

Ok, new test. Besides that i dont like the python errors shown, this still looks good. So i dont know.. See below, i can not make it error. for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do samba-tool dns add dc1.internal.dom.tld $x.249.10.in-addr.arpa 158 PTR host-test.extrazone.dom.tld ; done Record added successfully Record added successfully Record added successfully Record added