Displaying 20 results from an estimated 2000 matches similar to: "DNS problems when adding samba DC to win2008R2"
2020 Sep 13
3
DNS problems when adding samba DC to win2008R2
Hi Rowland, thank you for your help.
I've added the include "/var/lib/samba/bind-dns/named.conf in
/etc/bind/named.conf instead of named.conf.options.
As for the link, here it goes.
https://lists.samba.org/archive/samba/2019-July/224546.html
Best regards
Rowland penny via samba <samba at lists.samba.org> escreveu no dia domingo,
13/09/2020 ?(s) 17:11:
> On 13/09/2020 16:46,
2020 Sep 13
0
DNS problems when adding samba DC to win2008R2
On 13/09/2020 16:46, Carlos Jesus via samba wrote:
> Hello all,I'm trying to add a self compiled samba 4.12 DC to a Windows
> 2008R2 domain.Adding the samba DC was troublesome but successful (I had to
> modify join.py as I swa in another thread "Join Samba to a Windows AD
> ERR_DS_NO_CROSSREF_FOR_NC". After that I could join the samba DC and
> everything seemed ok.
2020 Sep 14
3
DNS problems when adding samba DC to win2008R2
Hai,
See below.
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Carlos Jesus via samba
> Verzonden: maandag 14 september 2020 11:40
> Aan: Rowland penny
> CC: sambalist
> Onderwerp: Re: [Samba] DNS problems when adding samba DC to win2008R2
>
....
> >
> >
> grep: /etc/samba/smb.conf: No such file or
2020 Sep 14
0
DNS problems when adding samba DC to win2008R2
Hi Louis thanks for the help,
> > Kerberos SRV _kerberos._tcp.MyDomain.lx.pt <http://tcp.mydomain.lx.pt/> record
> verified ok, sample
> > output:
> > Server: 192.168.59.112
> > Address: 192.168.59.112#53
> >
> > _kerberos._tcp.MyDomain.lx.pt <http://tcp.mydomain.lx.pt/> service
> = 0 100 88
> > dc2.MyDomain.lx.pt
2020 Sep 14
2
DNS problems when adding samba DC to win2008R2
>
> On 13/09/2020 22:40, Carlos Jesus wrote:
> > Hi Rowland, thank you for your help.
> > I've added the include "/var/lib/samba/bind-dns/named.conf in
> > /etc/bind/named.conf instead of named.conf.options.
> Please don't do that, it isn't a good idea, use an 'include', that way
> if something changes, it will still work.
> >
It IS an
2020 Nov 18
2
dnsupdate failed with TKEY is unaceptable
Rommel Rodriguez Toiracrommelrt at nauta.cu
On 18/11/2020 17:34, Rommel Rodriguez Toirac via samba wrote:>?? > In my network I have a samba 4.11.4 as Active Directory Domain Controller installed in CentOS 7 (gtmad.gtm.onat.gob.cu - 192.168.41.17). I have recently installed samba 4.13.2 in CentOS 8 (gtmad1.gtm.onat.gob.cu - 192.168.41.18) and following the wiki.samba.org guide I have joined
2019 Jan 11
2
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
On Friday, January 11, 2019 12:04 PM, Rowland Penny via samba <samba at lists.samba.org> wrote:
> OK, you are now running my scripts as found on the Samba wiki, so it
> should work.
>
> Lets check some things, can you post the contents of the following
> files:
>
> /etc/resolv.conf
search corp.<DOMAIN>.com# nameserver 172.20.10.131nameserver 172.20.10.130
2020 Feb 28
4
Samba Bind DLZ Slow queries
Hello All,
I hope you can assist me,
I'm running Bind DLZ with our Samba AD DC environment
Bind: BIND 9.11.4-P2-RedHat-9.11.4-9.P2.el7 (Extended Support Version)
Samba: Version 4.11.6-SerNet-RedHat-9.el7
OS: Red Hat Enterprise Linux Server release 7.7 (Maipo)
My DNS queries seems to be hanging intermittently, taking anything from
1sec - 15sec or even timing out.
I'm been monitoring the
2019 May 15
2
Workstations cannot update DNS
> > *named.conf.options*
> > options {
> > directory "/var/cache/bind";
> >
> > // If there is a firewall between you and nameservers you want
> > // to talk to, you may need to fix the firewall to allow
multiple
> > // ports to talk. See http://www.kb.cert.org/vuls/id/800113
> >
> > // If
2018 Feb 26
2
smbclient //server/netlogon -k -c 'ls' fails with "NT_STATUS_LOGON_FAILURE"
On Mon, 26 Feb 2018 12:27:56 +0200
Arcadie Cracan <arcadiec at gmail.com> wrote:
> Dear Rowland,
>
> I have commented out the 'idmap config' options, nothing changed.
> Here are my bind9 configs:
>
> /etc/bind/named.conf:
Nothing wrong there
>
> /etc/bind/named.conf.options:
> options {
> directory "/var/cache/bind";
>
2014 Sep 08
1
Starting second DC makes named to freeze on primary DC
hey,
first, i user bind 9.8.1 as my DNS backend
Well, I have a domain controller, dc1.example.com, running correctly and
with the following configurations...
== smb.conf ==
[global]
workgroup = EXAMPLE
realm = EXAMPLE.COM
netbios name = DC1
server role = active directory domain controller
idmap_ldb:use rfc2307 = yes
server services = -dns
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
2013 Mar 10
8
BIND Setup Issue
Dear All
I have a CentOS 6.3 machine. I am trying to setup DNS BIND setup in that
machine. It is having a static global IP. I have done lot of reading ,
google search and tried all possible option, but still not able to resolve
the issue.
My named.conf looks as below.
*
*
*
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only
2020 Mar 25
2
CentOS 6.10 bind DNSSEC issues
Hi,
??? Anyone else had any issues with CentOS 6.10 bind DNS server issues
this afternoon.
At 16:26 (GMT) had alerts for DNS failures against our CentOS 6.10 bind
DNS servers
from our monitoring system.
Sure enough DNS requests via the server was failing, checking the
named.log showed
dnssec issues;
25-Mar-2020 16:26:10.285 dnssec: info: validating @0xb48b17c0:
push.services.mozilla.com
2020 Apr 12
2
BIND9/DNS lookups stopped working after upgrading our Comcast modem/gateway
OK here's our setup, we're running pfSense as our firewall/router. We
have a dual-WAN with a Comcast Business Gateway and another local ISP.
We're running Samba 4.7.6 as the AD DC & Bind 9.9.4. Here's the issue,
we just upgraded our Comcast service to a higher speed & they replaced
the modem/gateway. Everything was working fine, before the modem swap.
Once they did
2019 May 15
2
Workstations cannot update DNS
> > > >
> >
https://wiki.samba.org/index.php/BIND9_DLZ_AppArmor_and_SELinux_Integration
> > > >
> > > > selinux is not installed.
> > > > Firewall is not active.
> > > > iptables is not active.
> > > The problem appears to have something to do with Apparmor.
> > > >
> > > > From that page,
>
2019 Aug 05
2
samba dlz. bind9 nslookup is wrong
On 05/08/2019 10:29, Patrik wrote:
> ok, so i remove that nemd.conf.update, but the rest it looks good?
> *_
> _*
These are my 'named.conf' files, used since 2012 with only minor changes:
/etc/bind/named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
2020 Feb 27
3
User names not replicating to secondary DC
> > DC1 smb.conf
> > winbind use default domain = true
> > winbind offline logon = false
> > winbind nss info = rfc2307
> > winbind enum users = yes
> > winbind enum groups = yes
>
> The above lines have no place in a DC smb.conf or are defaults
Commented them out.
>
> Change the following files as shown:
2014 Sep 21
1
rndc permission denied
Hi, h when I have the following problem with rndc:
[root at centos7 ~]# rndc recursing and
rndc: 'recursing' failed: permission denied
SELinux is disables:
named.conf config file is:
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See
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