similar to: bind9 won't run

Displaying 20 results from an estimated 7000 matches similar to: "bind9 won't run"

2016 Oct 16
1
bind9 won't run
On 2016-10-16 12:55, Rowland Penny via samba wrote: > On Sun, 16 Oct 2016 12:38:00 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with >> Bind9_DLZ. >> >> I have one machine just like this one. Same hardware, same software >> setup. First machine is
2016 Oct 16
0
bind9 won't run
On Sun, 16 Oct 2016 12:38:00 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with > Bind9_DLZ. > > I have one machine just like this one. Same hardware, same software > setup. First machine is working fine. > > At the moment this (second) machine is not joined to the other
2019 May 14
2
Workstations cannot update DNS
I am trying to get DDNS working, so workstations can update their ip. The domain is msi.mycompany.com The DC server works, as well as group policies. I set rights to these files > chgrp bind /var/lib/samba/private/ > chmod 750 /var/lib/samba/private/ > chgrp bind /var/lib/samba/private/dns.keytab > chmod 640 /var/lib/samba/private/dns.keytab journalctl shows this. May 14 14:22:32
2019 May 15
2
Workstations cannot update DNS
> From: Rowland penny via samba <samba at lists.samba.org> > To: samba at lists.samba.org > Date: 05/14/2019 02:50 PM > Subject: Re: [Samba] Workstations cannot update DNS > Sent by: "samba" <samba-bounces at lists.samba.org> > > On 14/05/2019 21:36, Durwin via samba wrote: > > I am trying to get DDNS working, so workstations can update their ip.
2017 Nov 27
2
Debian Buster, bind_dlz, and apparmor
Last week, Debian testing (Buster) added apparmor to the list of dependencies for its latest kernel release, apparently because systemd needs it.  Recently, I noticed my first casualty - bind9 - due to apparmor failures with bind_dlz. Here is the initial journalctl results: Nov 23 10:12:12 debpdc named[16080]: starting BIND 9.10.6-Debian <id:9d1ea0b> -f -u bind Nov 23 10:12:12 debpdc
2019 Dec 04
7
Upgrading from Debian Stretch to Buster, Van Belle package
Hello, I am preparing for upgrading from Debian Stretch to Buster. I am using Louis Van Belle's Samba packages. My current Samba version is: # smbstatus --version Version 4.7.7-Debian I can see that the Samba version that will be installed, when I upgrade from Stretch to Buster, will be the 4.11 since this is the current stable release... I would like to know if there are major changes
2019 May 04
2
Issues with bind9 dlz
Hi Rowland, Thank you. I think the 5 zones maybe a parsing issues somewhere. Also, the realms are in capital, must have been a typo. The UFW has been disabled and selinux is in a disbaled state /etc/bind/named.conf.options has options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you may need to
2019 May 05
1
Issues with bind9 dlz
Hi Rowland, The samba-tool dns zonelist 127.0.0.1 -U Administrator%xxxxxxxxxx | grep 'pszZoneName', gives Using binding ncacn_ip_tcp:127.0.0.1[,sign] Mapped to DCERPC endpoint 135 added interface eth0 ip=192.168.117.10 bcast=192.168.14.255 netmask=255.255.255.0 added interface eth0 ip=192.168.117.10 bcast=192.168.14.255 netmask=255.255.255.0 Mapped to DCERPC endpoint 1024 added interface
2016 Oct 08
2
reverse dns confused
I have built a second dtdc03 and joined to my first dtdc01. Thought all was well but, discovered that reverse dns is not correct on second dtdc03. root at dtdc03:~# host dtdc03 dtdc03.dtshrm.dt has address 192.168.16.49 root at dtdc03:~# host 192.168.16.49 Host 49.16.168.192.in-addr.arpa. not found: 3(NXDOMAIN) root at dtdc03:~# nslookup dtdc03 Server: 192.168.16.49 Address: 192.168.16.49#53
2016 Oct 08
2
reverse dns confused
On 2016-10-08 07:58, Rowland Penny via samba wrote: > On Sat, 08 Oct 2016 07:50:03 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have built a second dtdc03 and joined to my first dtdc01. Thought >> all was well but, discovered that reverse dns is not correct on second >> dtdc03. >> >> root at dtdc03:~# host dtdc03
2016 Dec 04
2
port 135 - NT_STATUS_CONNECTION_REFUSED
On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01
2018 Dec 09
2
Indexer worker small bug
Hello, I think I submitted this before, but I am not sure this has been addressed I am using AppArmor with Dovecot, without any issue. However, I think there is a bug in the indexer working, from what I can see, a missing trailing slash. See: ------------ Dec 09 14:35:53 portal2 kernel: audit: type=1400 audit(1544366153.379:3035): apparmor="DENIED" operation="file_mmap"
2018 Dec 10
2
Indexer worker small bug
On 2018-12-09 23:13, Timo Sirainen wrote: > On 9 Dec 2018, at 16.44, Andr? Rodier via dovecot <dovecot at dovecot.org> > wrote: >> >> Hello, >> >> I think I submitted this before, but I am not sure this has been >> addressed >> >> I am using AppArmor with Dovecot, without any issue. >> >> However, I think there is a bug in the
2016 Dec 04
1
port 135 - NT_STATUS_CONNECTION_REFUSED
On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running
2019 Jan 22
4
Samba BIND9_DLZ autoupdate PTR
Set auth-nxdomain yes; And stop/start bind9 Other source : https://blogs.technet.microsoft.com/teamdhcp/2015/09/10/a-description-of-the-dns-dynamic-update-message-format/ /snap The DNS Client and Server services support the use of dynamic updates, as described in Request for Comments (RFC) 2136, "Dynamic Updates in the Domain Name System." The DNS Server service allows dynamic
2020 Nov 18
3
dnsupdate failed with TKEY is unaceptable
On 18/11/2020 19:27, Rommel Rodriguez Toirac wrote: > > ?It is /etc/named.conf and /etc/samba/smb.conf > > > # cat /etc/named.conf > > > ??tkey-gssapi-keytab "/usr/local/samba/private/dns.keytab"; > > > include "/usr/local/samba/bind-dns/named.conf"; > OK, does the /usr/local/samba/bind-dns directory exist ? if it does, is the
2016 Nov 21
2
db check fails
On 2016-11-21 04:01, L.P.H. van Belle via samba wrote: > Hi Bob, > > Sorry for the late responce, i was out for the weekend. > > I saw you got it fixed, good. ;-) > > Good to know its a bug. Thanks Rowland for pointing that out. > > ( added that in the script. ) > > @Marc, this is nothing fancy. > > This script use the commands as the samba wiki
2016 Dec 04
2
port 135 - NT_STATUS_CONNECTION_REFUSED
I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is showing the following: root at dtdc03:~# tail -f /usr/local/samba/var/log.samba [2016/12/01 10:14:39.167794, 0] ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket) Failed to connect host 192.168.16.50 (aa03011a-94c2-4c52-bc60-6fd2f75d35e5._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED.
2018 Dec 10
1
Indexer worker small bug
Hello Timo, I will try this evening. Kind regards, Andr?. On 10 December 2018 07:56:26 GMT+00:00, Timo Sirainen <tss at iki.fi> wrote: >On 10 Dec 2018, at 7.50, Andr? Rodier <andre at rodier.me> wrote: >> >> On 2018-12-09 23:13, Timo Sirainen wrote: >>> On 9 Dec 2018, at 16.44, Andr? Rodier via dovecot ><dovecot at dovecot.org> wrote:
2019 Aug 05
6
samba dlz. bind9 nslookup is wrong
... From your output below.. >> Uncomment only single database line, depending on your BIND version << Then tell uss, why are 3 lines uncommented? I suggest, run : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize it where needed, and show me your server setup. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: