search for: upgradedn

...but i miss the PTR Record. I have a foreward and reverse lookup zone. I use 4.1.6 and use now 4.1.11. Before it worked. I read at the wiki out that the sam.ldb.d and dns/sam.ldb.d are hard links. I checked that and the hard link was broken. In the wiki there was the information to use the samba-upgradedns -dns-backend=BIND9_DLZ. I used that but it DONT fix the hard links... 1. Is this a Bug? After that i added the hard links manually again. orion:/ # ll -ia /var/lib/samba/private/sam.ldb.d/ total 38124 2872179 drwxr-x--- 2 root named 4096 Sep 8 22:04 . 1267513 drwxr-xr-x 7 root root...

...d penny via samba wrote: > I would clone the DC you want keep, move the clone away from the > domain (easiest way, unplug the ethernet) then remove the old dead DC > from this and ensure it works. If you want to use Bind9 and don't have > the 'dns-*' user, then run samba-upgradedns as I said earlier. > > Once you are sure just what to do, turn off the DC you don't want and > then carry out the clean up procedure you used on the clone. This > should get you back to just one DC. > > Rowland A bit more clarification and background info. Dc1 is a physic...

...ote: > >> I would clone the DC you want keep, move the clone away from the >> domain (easiest way, unplug the ethernet) then remove the old dead DC >> from this and ensure it works. If you want to use Bind9 and don't >> have the 'dns-*' user, then run samba-upgradedns as I said earlier. >> >> Once you are sure just what to do, turn off the DC you don't want and >> then carry out the clean up procedure you used on the clone. This >> should get you back to just one DC. >> >> Rowland > > A bit more clarification and...

Hi, I'm trying to recreate dns.keytab for a DC but there seems to be a database issue, delete says the dns user doesn't exist, but upgradedns says it does. CentOS 7.2 Samba 4.5.0 samba-tool user delete dns-dc01 ERROR(exception): Failed to remove user "dns-dc01" - Unable to find user "dns-dc01" File "/usr/local/samba/lib64/python2.7/site-packages/samba/netcmd/user.py", line 412, in run samdb.delete...

...r "named" - trying with and without SELinux - veryfing /etc/krb5.conf /usr/local/samba/etc/smb.conf and /etc/named.conf for oddities, but I'm at a loss. Both 4.8.3 machines were created from same template, just different host names and IP addresses. One machine works perfectly fine (upgradedns finishes in ~2 seconds or less), other one needs 5 minutes per entry (times 20+... yeah, forever). What I already checked: obviously connection between both boxes exists (replication works fine for example) both machines are VM's running inside same hypervisor, Right now both DC's use e...

On 18/07/19 11:42, Rowland penny via samba wrote: > Well, 'dns-dc2' is the user for Bind9 on dc2, so you shouldn't try to > create it yourself. > > Easiest way will be to remove all mention of the dead DC, then use > 'samba_upgradedns' to upgrade to the internal dns server, then run it > again to upgrade to Bind9 again, this will create the required user > for you. > > Rowland I'm not sure if your advice applies. What I'm trying to achieve is to trick dc2 to forget about dc1 so I can demote dc2. Dc1...

...s it matter for replication which backend is being used? Or is everything expected to fully populate regardless of the DNS backend choice? > I would ensure your clients only use DC1 What's the best way to achieve it? Through a local firewall? > turn off Bind9 on DC2 and then run samba-upgradedns to use the > internal dns server, this will cure one of your problems. You may have > to delete the 'dns-dc2' user manually. There is more to it than just > renaming 'dns-dc2' to 'dns-dc1'. > > If you then want to demote DC2, you will need to get into idma...

...> run [2019/01/02 19:19:00.472301, 0] > ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) > /usr/sbin/samba_dnsupdate: raise e > > and so on... > > After downgrading from 4.9.2 back to 4.7.3 I experienced the same, > and I could fix it by running "samba_upgradedns > --dns-backend=BIND9_DLZ" (at least I guess this fixed it). The > results of this command were basically the same as on the wiki page. > But this time the result was exactly the same as with 4.9.2: > > isa:~/# samba_upgradedns --dns-backend=BIND9_DLZ > Reading domain infor...

Can you try to upgrade to any 4.8 version then to 4.9.4? might work, atleast my guess this will have a better chance get passed this bug. Greetz, Louis > Op 31 dec. 2018 om 18:35 heeft Král Gergely via samba <samba at lists.samba.org> het volgende geschreven: > > 2018-12-31 17:29 id??pontban Rowland Penny via samba ezt írta: > >>> >> >> OK,

...; ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) >>> /usr/sbin/samba_dnsupdate: raise e >>> >>> and so on... >>> >>> After downgrading from 4.9.2 back to 4.7.3 I experienced the same, >>> and I could fix it by running "samba_upgradedns >>> --dns-backend=BIND9_DLZ" (at least I guess this fixed it). The >>> results of this command were basically the same as on the wiki page. >>> But this time the result was exactly the same as with 4.9.2: >>> >>> isa:~/# samba_upgradedns --dns-bac...

...samba wrote: > On 18/07/19 11:42, Rowland penny via samba wrote: > >> Well, 'dns-dc2' is the user for Bind9 on dc2, so you shouldn't try to >> create it yourself. >> >> Easiest way will be to remove all mention of the dead DC, then use >> 'samba_upgradedns' to upgrade to the internal dns server, then run it >> again to upgrade to Bind9 again, this will create the required user >> for you. >> >> Rowland > > I'm not sure if your advice applies. > What I'm trying to achieve is to trick dc2 to forget about...

...of the DNS > backend choice? Just as long as a DC can find the other DC's, replication should occur. > >> I would ensure your clients only use DC1 > > What's the best way to achieve it? > Through a local firewall? > >> turn off Bind9 on DC2 and then run samba-upgradedns to use the >> internal dns server, this will cure one of your problems. You may >> have to delete the 'dns-dc2' user manually. There is more to it than >> just renaming 'dns-dc2' to 'dns-dc1'. >> >> If you then want to demote DC2, you will n...

...h before cmocka.h. o Bj?rn Jacke <bjacke at samba.org> * BUG 14122: docs-xml/winbindnssinfo: Clarify interaction with idmap_ad etc. o Volker Lendecke <vl at samba.org> * BUG 14251: smbd: Fix the build with clang. o Gary Lockyer <gary at catalyst.net.nz> * BUG 14199: upgradedns: Ensure lmdb lock files linked. o Anoop C S <anoopcs at redhat.com> * BUG 14182: s3: VFS: glusterfs: Reset nlinks for symlink entries during readdir. o Andreas Schneider <asn at samba.org> * BUG 14101: smbc_stat() doesn't return the correct st_mode and also the...

...ve from BIND9_FLATFILE to SAMBA_INTERNAL_DNS. I am using Samba version 4.1.17. During provisioning (some years ago) I have decided to use BIND9_FLATFILE. At this moment I would like to upgrade to Samba 4.4.2 and I would like to migrate to SAMBA_INTERNAL DNS. I have noticed the command "samba_upgradedns" but unfortunately I could not find information about migrating from BIND9_FLATFILE to SAMBA_INTERNAL DNS. I have found some information but it dates from 2012 and I am not sure if this still would work (http://samba.2283325.n4.nabble.com/migration-bind9-flat-file-to-DLZ-td4320796.html). I w...

...samba/netcmd/dns.py", line 940, in run [2019/01/02 19:19:00.472301, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: raise e and so on... After downgrading from 4.9.2 back to 4.7.3 I experienced the same, and I could fix it by running "samba_upgradedns --dns-backend=BIND9_DLZ" (at least I guess this fixed it). The results of this command were basically the same as on the wiki page. But this time the result was exactly the same as with 4.9.2: isa:~/# samba_upgradedns --dns-backend=BIND9_DLZ Reading domain information DNS accounts already...

...ecke <vl at samba.org> * BUG 14175: ctdb-tcp: Close inflight connecting TCP sockets after fork. o Stefan Metzmacher <metze at samba.org> * BUG 14153: s4:dirsync: Fix interaction of dirsync and extended_dn controls. o Gary Lockyer <gary at catalyst.net.nz> * BUG 14199: upgradedns: Ensure lmdb lock files linked. o Anoop C S <anoopcs at redhat.com> * BUG 14182: s3: VFS: glusterfs: Reset nlinks for symlink entries during readdir. o Christof Schmitt <cs at samba.org> * BUG 14140: wscript: Remove checks for shm_open and shmget. o Andreas Schneider &...

...01, 0] > > ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) > > /usr/sbin/samba_dnsupdate: raise e > > > > and so on... > > > > After downgrading from 4.9.2 back to 4.7.3 I experienced the same, > > and I could fix it by running "samba_upgradedns > > --dns-backend=BIND9_DLZ" (at least I guess this fixed it). The > > results of this command were basically the same as on the wiki page. > > But this time the result was exactly the same as with 4.9.2: > > > > isa:~/# samba_upgradedns --dns-backend=BIND9_DLZ...

...327(samba_runcmd_io_handler) > >>> /usr/sbin/samba_dnsupdate: raise e > >>> > >>> and so on... > >>> > >>> After downgrading from 4.9.2 back to 4.7.3 I experienced the same, > >>> and I could fix it by running "samba_upgradedns > >>> --dns-backend=BIND9_DLZ" (at least I guess this fixed it). The > >>> results of this command were basically the same as on the wiki page. > >>> But this time the result was exactly the same as with 4.9.2: > >>> > >>> isa:~/# sa...

...ation about the DNS zone in the directory. There is also an internal DNS server (but which does not support secure DNS updates at this time) and the flat file BIND 9.8 backend (storing the data in traditional zone files). To migrate from zone files to directory based DNS servers, a migration tool (upgradedns) has been added. samba-tool dns commands to manage DNS records stored in directory. smbwrapper (a user-space file system based on LD_PRELOAD) has been removed. Improvement to the upgrade process between Samba 3.x domains and Samba 4.0 AD domains (samba-tool domain samba3upgrade). Some major...

Hello List, I am trying to compile and install Samba 4 using the wiki guide on Centos 6.2. I am currently using the current source from git. It seems that the zone file used for Bind is not configured and not installed in the private directory. Is there any way to get this file generated so I can finish my install? Thank you for your time and have a great day!! Kind regards, Jeremy