Displaying 20 results from an estimated 10000 matches similar to: "Configuring the BIND9_DLZ module"
2018 Jul 28
1
Configuring the BIND9_DLZ Module
I have configured DNS BIND, but at the time of restarting bind I get
permission denied message in the file /var/lib/samba/private/named.conf.
The file has been edited, where the module for the BIND version was
decompressed, in addition to the owner being changed to the file, however,
the same message still appears. Should a special permission be applied?
root @ adsserver: / etc / netplan # ll
2018 Jul 26
1
NTP Selinux Permissions
I have installed samba AD in centos 7, but I have an inconvenience to
synchronize my clients with the NTP service, the status is in failed, it
has to do with the socket. What permissions should be assigned?
[root @ adsserver ~] # systemctl status ntpd
● ntpd.service - Servicio de hora de red
Cargado: cargado (/usr/lib/systemd/system/ntpd.service; habilitado;
proveedor preestablecido:
2018 Jul 30
0
Internal DNS migrate to Bind9_DLZ
On Mon, 30 Jul 2018 10:41:14 +0200
Eben Victor via samba <samba at lists.samba.org> wrote:
> Hello,
>
> I hope that someone can perhaps assist me or just guide me in the
> right direction.
>
> I've been following all the steps for setting up and migrating my
> Samba Internal DNS to Bind9_DLZ.
> https://wiki.samba.org/index.php/Setting_up_a_BIND_DNS_Server
>
2018 Jul 31
3
Internal DNS migrate to Bind9_DLZ
> So, you are using Samba without problem, it is just that when you try
> to use Bind9 instead of the internal dns server, your problems start.
>
> Let's just recap
>
> You have run 'samba_upgradedns'
> You have altered smb.conf
> You have configured 'named.conf' correctly
> The Samba 'named.conf' file is readable by 'named' (this
2018 Jul 30
2
Internal DNS migrate to Bind9_DLZ
Hello,
I hope that someone can perhaps assist me or just guide me in the right
direction.
I've been following all the steps for setting up and migrating my Samba
Internal DNS to Bind9_DLZ.
https://wiki.samba.org/index.php/Setting_up_a_BIND_DNS_Server
https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End
But this doesn't seem to work for me, I can get bind started up 100% when I
remove
2018 Jul 26
4
(no subject)
Tengo instalado samba AD en centos 7, pero tengo un inconveniente para
sincronizar mis clientes con el servicio NTP, el estado esta en failed,
tiene que ver con el socket. Que permisos se le debe de asignar?
[root @ adsserver ~] # systemctl status ntpd
● ntpd.service - Servicio de hora de red
Cargado: cargado (/usr/lib/systemd/system/ntpd.service; habilitado;
proveedor preestablecido:
2018 Jul 26
0
(no subject)
Ivan la mayoría en esta lista responde en ingles, tienes qué configurar tu servidor ntp para que los clientes sincronicen bien la hora
** Alcatel Onetouch Idol 3 (5.5) **
en 26/07/2018 01:03, Ivan Rojas via samba <samba at lists.samba.org> escribió:
>
> Tengo instalado samba AD en centos 7, pero tengo un inconveniente para
> sincronizar mis clientes con el servicio NTP, el
2018 Jun 30
0
BIND9_DLZ: TKEY is unacceptable - depending on the name server
On Sat, 30 Jun 2018 18:08:22 +0200 (CEST)
"Peter Serbe" <peter at serbe.ch> wrote:
>
>
> Rowland Penny via samba schrieb am 30.06.2018 16:45:
>
> > I think you have run into the 'whoever creates the dns records owns
> > them' problem.
>
> Hi Rowland,
>
> I am extremely surprised by that. Writing the two lines below each
>
2018 Jul 30
8
Internal DNS migrate to Bind9_DLZ
Hello Rowland,
See below as requested.
/etc/named.conf
# Global Configuration Options
include "/var/lib/samba/bind-dns/named.conf";
options {
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
auth-nxdomain yes;
directory
2019 Sep 01
3
Problems with Internal DNS Samba 4
Hi,
I'm folowing the tutorial:
https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End
But, the follows file there isn't in my DC, so can I to create it manually?
/usr/local/samba/bind-dns/named.conf file and uncomment the module for your
BIND version. For example:
dlz "AD DNS Zone" {
# For BIND 9.10
database "dlopen
2019 Aug 31
0
Problems with Internal DNS Samba 4
On 31/08/2019 04:28, Marcio Demetrio Bacci via samba wrote:
> Hi,
>
> I have updated my DC's to Samba 4.10.7, but I still can't add a new DC to
> the domain. I believe the problem is with Samba Internal DNS.
>
> So I would like to convert my DNS from Internal DNS to Bind9_DLZ of the
> production DC's. Then I will join a new DC to the domain to see if it works.
2019 Nov 25
0
Problems setting up samba bind9_dlz on Ubuntu 18.04
That link your using has few poing that needs fixing.. Its not a bad exampl.e
For example. 5. apt-get install ntpdate.. Should be : apt-get install ntp
You should configure the NTP daemon also on the AD-DC.
Point (step 3)
10.
systemctl stop samba-ad-dc smbd nmbd winbind
Also needs
systemctl stop disable smbd nmbd winbind
systemctl stop mask smbd nmbd winbind
12.
winbind enum users =
2018 May 09
0
Samba4 on Ubuntu 18.04 Howto setup ADDC with bind9_DLZ
I was rereading this i missing one thing, my dislectic got me again..
In the last part.
Just before all systemctl's.
This :
and we change the systemd-resolved and point it to the IP ( NOT localhost ) of the server
now change the systemd-resolvd DNS.
sed "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf
The sed line should be :
sed -i
2018 Aug 05
1
samba configuration
How can I get all the users who deleted the files and folders in the
recycling folder, I have configured it and I delete folders with different
users of the active directory but it only comes from a user, I send the
complete configuration so that they can help.
----
# Global parameters
[global]
workgroup = SOPORTE
realm = SOPORTE.LOCAL
netbios name = ADSSERVER
2018 May 09
0
Samba4 on Ubuntu 18.04 Howto setup ADDC with bind9_DLZ (extra part 4.8.1 samba)
Hai,
I detected a minor error and i added a quick fix.
And i'm testing my 4.8.1 debian package on ubuntu 18.04, see below..
Syslog shows.
May 9 14:50:26 ubuntu1804 systemd[9448]: /lib/systemd/system-generators/netplan failed with exit status 1.
The fix is: editor /etc/netplan/01-netcfg.yaml
The last adresses: needs a server adres.
cat /etc/netplan/01-netcfg.yaml
# This file describes
2018 Feb 06
0
Samba Migration and AD integration
On Tue, 6 Feb 2018 11:01:52 +0000
Praveen Ghimire <PGhimire at sundata.com.au> wrote:
> Hi Rowland,
>
> Thank you.
>
> Yes to the first point.
>
> We are using Bind9 but to continue using it is not necessarily set in
> stone.
If you are going to have more than one AD DC, then using Bind9 makes
sense.
> If using Samba Internal DNS makes more sense then we can
2020 Apr 06
2
Any advice for installing Samba as an AD server on Raspbian Buster with BIND9 and ISC DHCP?
Thanks for your advice, Rowland
> > Yes, I am setting up a new Samba-based AD DC.
> If you are joining? to an existing domain, then you cannot be setting up
> a new domain ;-)
Yes - joining a new DC to an existing domain.
> > Should I install BIND9 and DHCP first, then install Samba and do the join?
>
> I personally would do it in stages, set up the Rpi, add
2018 Jul 30
4
Internal DNS migrate to Bind9_DLZ
It is part of the Sernet packages and is currently on 1.3.4
/usr/lib64/samba/libldb.so.1.3.4
We started using sernet-samba-ad from v4 using the internal dns and updated
as versions were released. We have now recently updated from 4.8.2 to 4.8.3
and still using internal dns.
Our DNS is working as it should, it's only been since recently that we have
to migrate to bind9.
On Mon, Jul 30, 2018
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
Hi Roger,
I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS
backend, Bind is 9.9.4 and I don't have that issue.
I tried reload my bind using systemctl at first and no issue, then I tried
"rdnc reload" to be sure rndc was used, still no issue.
By no issue I don't mean log are clean, I mean the DNS service is working
well (tested using dig commands).
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
I've added logs (dirty and quickly):
logging {
channel "request" {
file "/var/named/named.run" size 10m;
print-time yes;
print-category yes;
severity debug;
};
category default { request; };
category security { request; };
};
Reload DNS service using systemctl once, twice, then restart Bind, reload
it using rndc and no complain about log file and