similar to: debian wheezy sernet samba 4.2.1 : DC Joined and : samba_dnsupdate:update failed: NOTAUTH

Hai Marco, Yes, best is to use the "localhost" dns setup as caching/forwarder only. All you need is for the forwarding is : zone "your.dnsdomain.tld" { type forward; forwarders { IP_DC1; IP_DC2; }; }; zone "168.192.in-addr.arpa" { type forward; forwarders { IP_DC1; IP_DC2; }; }; If you think its still to slow, remove > options attempts:2

Hello guys, hope you're doing good: I'm running a couple of Samba servers like follows: Primary DC ========= Platform: Zentyal 4.2 development x68_64 Samba: 4.3.4-Zentyal DNS: BIND9_DLZ_module Role: Primary Domain Controller Setup: By default, following Zentyal's web interface. Secondary DC =========== Platform: CentOS 7 x86_64 Samba: 4.3.4 built from source DNS: SAMBA_INTERNAL

Hello, I'm trying to join a samba 4 DC to an already existing samba 4 DC, both with BIND9_DLZ. Samba is at version 4.4.5, bind is version 9.10.4-P1, all brand new. The existing DC runs fine, but the added DC refuses to update its local bind database: every attempt to update the local DNS results in "update failed: NOTAUTH". AD replication works perfectly. Both systems are set

On 22/02/16 12:49, Jason Voorhees wrote: > Hello guys, hope you're doing good: > > I'm running a couple of Samba servers like follows: > > Primary DC > ========= > Platform: Zentyal 4.2 development x68_64 > Samba: 4.3.4-Zentyal > DNS: BIND9_DLZ_module > Role: Primary Domain Controller > Setup: By default, following Zentyal's web interface. > >

On 18.07.2016 20:10, Rowland penny wrote: > On 18/07/16 00:02, Norbert Hanke wrote: >> Hello, >> >> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >> 9.10.4-P1, all brand new. >> >> The existing DC runs fine, but the added DC refuses to update its >>

On 18.07.2016 01:52, Achim Gottinger wrote: > > > Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >> Hello, >> >> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >> 9.10.4-P1, all brand new. >> >> The existing DC runs fine, but the added DC refuses to update

Hai Ole, What does this give you as output? host bpn.tu-berlin.de I assum you dnsdomain name is the same as your REALM_NAME ? For me it show the 2 ipadresses of my DC's. And my MX record. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens James > Verzonden: woensdag 6 januari 2016 19:10 > Aan: samba at

For the member servers, to reduce timeouts etc when one DC is down. Change your resolv.conf to : domain internal.domain.tld search internal.domain.tld nameserver IP_DC1 nameserver IP_DC2 options timeout:2 options attempts:2 options rotate options edns0 see man resolv.conf for the options explained. Ow.. and .. domain and search are NOT exclusive anymore in Debian Jessie and up. At least,

Hai marco, Well, this is a hard one to answer for me. I'll give it a try. ;-) > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Gaiarin via samba > Verzonden: vrijdag 2 augustus 2019 15:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] winbind seems to hang when the DC goes > down instead of switching

Am 18.07.2016 um 01:02 schrieb Norbert Hanke: > Hello, > > I'm trying to join a samba 4 DC to an already existing samba 4 DC, > both with BIND9_DLZ. Samba is at version 4.4.5, bind is version > 9.10.4-P1, all brand new. > > The existing DC runs fine, but the added DC refuses to update its > local bind database: every attempt to update the local DNS results in >

On 18/07/16 00:02, Norbert Hanke wrote: > Hello, > > I'm trying to join a samba 4 DC to an already existing samba 4 DC, > both with BIND9_DLZ. Samba is at version 4.4.5, bind is version > 9.10.4-P1, all brand new. > > The existing DC runs fine, but the added DC refuses to update its > local bind database: every attempt to update the local DNS results in >

On 18.07.2016 22:48, Achim Gottinger wrote: > > > Am 18.07.2016 um 11:45 schrieb Norbert Hanke: >> On 18.07.2016 01:52, Achim Gottinger wrote: >>> >>> >>> Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >>>> Hello, >>>> >>>> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >>>> both with

On 18/07/16 21:31, Norbert Hanke wrote: > On 18.07.2016 20:10, Rowland penny wrote: >> On 18/07/16 00:02, Norbert Hanke wrote: >>> Hello, >>> >>> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >>> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >>> 9.10.4-P1, all brand new. >>> >>> The

Please don't post any sensitive information - even if I forget sanitizing it. This is probably the reason behind it: Our corporate DNS servers hold info about our machines. This works together with DHCP. By registering the machines I simply prevent any IP conflicts. My domain DNS has nothing to do with it. In my domain members (Win clients and Linux servers) only my DCs are set as DNS

Hai, well, Close.. I see multiple errors which makes that DNS setup isnt working. We have multiple ways to setup networking these days, which also makes things more confusing.. - old style. /etc/network/interfaces - netplan /etc/netplan/00-installer-config.yaml - systemd /etc/systemd/network/lan-devX.network > > > probably isn't, if netplan is being used :-) > >

Im suggesting, Since the following: NOTAUTH : is a failure on dns updates is OR incorrect manual changes in bind and/or incorrect rights. And check the needed rights on what the dns needs. I dont know if your using bind or internal dns. For bind : look here https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD And for the NTP Server config. Dont use a pool, use a

Am 18.07.2016 um 11:45 schrieb Norbert Hanke: > On 18.07.2016 01:52, Achim Gottinger wrote: >> >> >> Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >>> Hello, >>> >>> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >>> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >>> 9.10.4-P1, all brand

Ok, some more resolving things to fix.   On both DC's few things to edit. In resolv.conf, the order is important here and dont point to nameserver 127.0.0.1 for the DC's.   DC1. file: /etc/resolv.conf  search example.corp nameserver IP_DC1 nameserver IP_DC2 nameserver 8.8.4.4 /etc/hosts IP_DC1 hostname.internal.example.com hostname IP_DC2 hostname.internal.example.com hostname     

Ok .. maybe if seen something, dont know for sure, so Rowland, what do you think about below. Post the result of : klist -e -k /etc/krb5.keytab i see in your logs. AS key obtained for encrypted timestamp: aes256-cts/000A In my setup, i dont have aes256-cts available in my keytab, do you? You can try adding this, to krb5.conf. ; for Windows 2003 ; default_tgs_enctypes = rc4-hmac

Hello Rowland, thanks for your help. My replies lines below: > Do the DCs point at each other for dns ? > > i.e. is /etc/resolv.conf on the first DC something like this: > > search your.domian.com > nameserver ip.of.second.dc > nameserver ip.of.this.dc > > and on the second DC: > > search your.domian.com > nameserver ip.of.first.dc > nameserver