similar to: samba wiki

Hai, ? Is there any way to stop the updateing of named.conf.update?(bind9_dlz) ? I need to be able to add 1 line to this file. ? if its not possible then i must use bind9_flatefile, but i want to use the bind9_dlz modules since this is the only one which supports multi master dns. ? ? Best regards, ? Louis ?

Thanks for the info, At the moment, I don't have more than 1 DC, but I am planning on doing the bind master/slave thing thing soon using the Linux webserver host. With failover, I don't see why that wouldn't work with multiple DCs (but of course haven't tried yet). In any case, our AD/DC also hosts mail and redirected folders do if it goes down we've got big problem anyway --

I've used the Samba AD DC HOWTO <https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO> to install Samba 4 as an Active Directory/Domain Controller. I've successfully configured the domain/realm and DNS (as far as I can tell) and worked my way through Testing Your Samba Domain Controller <https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO#Testing_Your_Samba_Domain_Controller>

Hi list I have a problem and I hope anyone here can provide me a solution to my problem. I have a Samba4 Server installed on a hosted platform with bind9 flatfile backend. The OS is Ubuntu 12.04 LTS. All tests on the server succeeded. Name resolution works fine and also the sambaclient -L localhost -U% is successful. Whenever I try to join the domain with my Win8 machine I get the

Hello Together Please i have here a little company with any exisiting internal DNS Server "BIND 9.11.5-P4-5.1-Debian (Extended Support Version) <id:998753c>" Today i compilled the release Samba 4.10.7 successfully on any new machine here..... i read on Samba org the following News. - Do not use the BIND9_FLATFILE DNS back end. It is not supported and will be removed

Hi, Reproduced error with internal dns and bind_dlz, on both situations with a new provisioned domain 2016-06-10 18:27 GMT+02:00 Trenta sis <trenta.sis at gmail.com>: > Hi, > > I have made all dns test and other tests decribed in > https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller#Testing_DNS > with success > > We use dns bind_dlz, all

Dear all, I have a few question regarding to DNS and upgrading from Samba 4.1.17 to 4.4.2. After reading about the Badlock Bug, I feel the urge to upgrade my Samba installation and to move 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've been using bind9 and DHCP on Samba 4.1.0 thru 4.1.17 and Slackware 64 14.1 for many months now in a production environment and it works just fine. There are a few tweaks here and there to get bind/dhcp to play nicely with Samba ... Note, conf file locations are Slackware, but you'll know where the same thing goes in your distro. In the examples below, my Domain IP range is

On Sat Jan 28 02:37:16 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > On 28/01/2023 06:44, Mark Foley via samba wrote: > > I wrote earlier about setting the domain user password minimum to > 14 > > characters. It was advised that my first step should be to upgrade from Samba > > 4.8.2 to the most recent version available which for my Slackware 15.0

On 13/02/15 22:48, Steve Ankeny wrote: > Thanks for the quick response! > > Do I still need the following packages? > > adam at sogo:~$ sudo dpkg --get-selections | grep krb5 > krb5-config install > krb5-user install > libgssapi-krb5-2:amd64 install >

Hi Marc, Thanks for getting back to me. Marc Muehlfeld wrote on 24-2-2015 21:12: > Hello Bram, > > Am 24.02.2015 um 12:37 schrieb Bram Matthys: >> Is there a way to re-initialize/re-provision DNS? > > No. > That would be a pitty. >> well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but >> from a users' point of view everything

When I run: # samba_upgradedns --dns-backend=BIND9_DLZ I get the following: lpcfg_load: refreshing parameters from /etc/samba/smb.conf params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Reading domain information lpcfg_load: refreshing parameters from /etc/samba/smb.conf params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" DNS

On 28/01/2023 06:44, Mark Foley via samba wrote: > I wrote earlier about setting the domain user password minimum to > 14 > characters. It was advised that my first step should be to upgrade from Samba > 4.8.2 to the most recent version available which for my Slackware 15.0 distro is > 4.15.5. This also involved a distro upgrade from Slackware 14.2 to 15.0. > > After

Hi, Is there a way to re-initialize/re-provision DNS? I have a working domain with 100+ users and computers etc.. I want to preserve all those users, settings and group policies etc, only start the DNS part from scratch. Why? I've been having some (mysterious) issues with Samba 4 DNS since.. well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but from a users' point of

Hello Bram, Am 24.02.2015 um 12:37 schrieb Bram Matthys: > Is there a way to re-initialize/re-provision DNS? No. > well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but > from a users' point of view everything worked fine.. it was mostly the DNS > management from group policy that wasn't working. > ... > Today I wanted to install 4.1.17 but after

I have been wanting to allow our routers to continue to serve dhcp thinking this would give us a safer fail environment. Now we are learning that our routers can handle creating a whitelist of mac addresses to use for dhcp leases. So we need to look at alternatives. I am wondering how many samba AD DC's also run dhcp -- and if there is a samba 'good practice' for managing dhcp. Yes, I

To all, I have run into a problem. I am running Samba 4.1.0 pre1-git-94f11e9 and I shut down our server to do regular maintenance. Unknown to me at the time, a machine was connected. I know, ugh!! Anyway, when I rebooted and tried to use the AD users and groups tool, I get an error stating that "naming convention cannot be located because the system detected a possible attempt to

On 05/08/2019 09:55, Patrik via samba wrote: > the dig is wrong as well, it adds an additional ip address, which i have > not request to use other interfaces: > root at server:/# dig p3x-dc.patrikx3.com > Patrik, I have told you what your problem is, refusing to accept that you have setup Bind9 incorrectly is no reason for opening a new thread. Just in case you missed it, or

Rowland penny wrote on 3/18/16 12:58 PM: > On 18/03/16 19:27, Robert Moulton wrote: >> Rowland penny wrote on 3/18/16 11:48 AM: >>> On 18/03/16 18:19, Robert Moulton wrote: >>>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>>> something odd. When I run 'samba-tool fsmo show' I get an error: >>>> >>>> #

I am trying to setup an AD using a Linux server to get away from Windows Server 2008. So far I have tried the setup on both a Debian 7.4 64 bit machine, and a Raspberry Pi (Debian variant). I've tried both Samba stable versions 4.1.6 and 4.1.7, and they both give me the same results. I followed the instructions to install the Samba 4 AD setup at