search for: autoritative

Is there a specific way to set a name server so that clients are always *forced* to use an autoritative name server? UltraDNS and some others have mentioned little features they have, but it only hints at the possibility that somewhere in the DNS spec. -karlski

Hi all, I am having the same issue that is described in an older thread here: https://lists.samba.org/archive/samba/2018-February/213656.html The problem I am facing is that the machine accounts are not trusted in the domain (this is true for all Win 10 Systems). The issue with the computer is from my pov: Folgende herausgefilterte Gruppenrichtlinien werden nicht angewendet.

Hi Rowland, On 20.10.19 19:16, Rowland penny wrote: > On 20/10/2019 16:52, Martin Tessun via samba wrote: >> Hi all, >> >> I am having the same issue that is described in an older thread here: >> https://lists.samba.org/archive/samba/2018-February/213656.html >> >> The problem I am facing is that the machine accounts are not trusted >> in the domain

Client's credentials have been revoked .. Means the Active Directory account to which the keytab is related has been disabled, locked, expired, or deleted. Thats the first thing that needs to be verified. Also the bind config. If its an DC, in global options add: auth-nxdomain yes; Your DC = the Autoritive server of your domain.. ( a quick look ) Greetz, Louis >

On 20/10/2019 16:52, Martin Tessun via samba wrote: > Hi all, > > I am having the same issue that is described in an older thread here: > https://lists.samba.org/archive/samba/2018-February/213656.html > > The problem I am facing is that the machine accounts are not trusted > in the domain (this is true for all Win 10 Systems). The issue with > the computer is from my

On 10/20/19 11:52 AM, Martin Tessun via samba wrote: > Hi all, > > I am having the same issue that is described in an older thread here: > https://lists.samba.org/archive/samba/2018-February/213656.html The description of that link, says it is running Samba AD with MIT Kerberos. the MIT backend is experimental and this is one of the problems it has, machine GPOs don't work.

Hi, I set up a webserver with Apache on one of the machines on the local network. There's a DNS configured for the LAN, with a dummy domain name (presbytere.local), and every machine is pingable by its hostname. The webserver runs on the machine 'buildbox'. The webserver actually has two (static) websites on it, for testing and fiddling purposes. Each site's pages are stored

Hi all, On 21.10.19 17:38, Martin Tessun wrote: > Hi Rowland, > > On 20.10.19 19:16, Rowland penny wrote: >> On 20/10/2019 16:52, Martin Tessun via samba wrote: >>> Hi all, >>> >>> I am having the same issue that is described in an older thread >>> here: https://lists.samba.org/archive/samba/2018-February/213656.html >>> >>>

Hai guys, After a few messages on the list on Buster, i decided to upgrade one of my production AD-DC's and see what happens. If noticed a few things here, so here are the steps and changes i made to upgrade and have a correct working AD-DC after the upgrade. Setup is as followed: Debian Stretch AD-DC with Bind9 DLZ and ntp time. This is still the base i used for my AD-DC

I've summerized a bit.. And i saw Rowland also answered already. Below is anonimized, but it shows, 2 completely different server setups. I really suggest you setup your AD-DC's the same. To summ up. DC1 Samba is running as an AD DC but 'winbindd' is NOT running. You running SSSD on the AD-DC, which is not supported. Your using a really out-dated OS.. The hosts is not

Hi all, I have an old dc (4.0.9). Let's call it dc1. I also have a new one (4.5.16) which I'm planning to switch to. Let's call it dc2. After initial set up of dc2 I initialised replication and things looked ok for a couple of weeks. Recently I've managed to mess it up. Possibly by editing users and DNS records. Or copying Kerberos cache and trying to use it elsewhere for

Hi Louis, Just an update on this. I ran up a new test LXC container and completely removed apparmor. Then install the packages. I got the same errors I thought I would change the DNS from Bind to internal and back to bind. The following is going from Bind9 to Internal root at server5-ad:/var/log# service bind9 stop root at server5-ad:/var/log# systemctl mask bind9 Created symlink

Hai, You posted the correct things here, for a quick fix i I'm buzzy with something else atm but i saw that /dev/urandom part. Add in the bind9 (named) apparmor profile # Samba DLZ /{usr/,}lib/@{multiarch}/samba/bind9/*.so rm, /{usr/,}lib/@{multiarch}/samba/gensec/*.so rm, /{usr/,}lib/@{multiarch}/samba/ldb/*.so rm, /{usr/,}lib/@{multiarch}/ldb/modules/ldb/*.so rm,

Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The

Hi Louis, Thank you for that I have made the changes as per below , some items might have duplicated. I then reload apparmor restarted the samba-ad-dc and bind9 services and get the same issue. Every time the forward DNS update works but the reverse doesn't I found a really interesting samba post going back 2017 re the DHCP and DNS