similar to: DNS entry missing after join to ad

Displaying 20 results from an estimated 9000 matches similar to: "DNS entry missing after join to ad"

2020 Sep 10
1
DNS entry missing after join to ad
I have restart bind and samba multiple times. I records are missing but i do not what to add them all manually. On 10.09.20 16:34, L.P.H. van Belle via samba wrote: > Looks like you forgot to start bind9 before you started samba.. > After the join.. > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> basti
2019 Sep 03
3
Trouble joining DC Bind9_DLZ
On 03/09/2019 10:07, Marcio Demetrio Bacci via samba wrote: > Hi, > > I'm using Samba 4.10.7 with Bind9_DLZ (9.10.3-P4-Debian), but I'm not > getting to insert a new DC into the Domain. My SO is a VM Debian 9.9. > > Following is the command used and the error: > > root at samba4-dc3:/var/lib/samba/private# samba-tool domain join > empresa.com.br DC -k yes
2020 Sep 11
3
dnsvi and bind_dlz
Hello is there a way to use dnsvi with samba bind_dlz? When i use this i get error update failed: NOTAUTH
2017 Nov 08
2
Samba 4.7 DC with BIND9_DLZ and MIT Kerberos fails at DNS Update
On Tuesday, 7 November 2017 21:04:09 CET Marc Muehlfeld wrote: > Hi Johannes, > > Am 07.11.2017 um 18:35 schrieb Johannes Engel via samba: > > a month ago I have filed bug #13066 about Samba 4.7 DC using BIND9_DLZ > > as DNS backend failing to run samba_dnsupdate using MIT Kerberos. The > > logs show a kerberos error "Request is a replay". Logs attached here:
2016 Sep 23
3
dnsupdate_nameupdate_done - Failed DNS update
Thank you Denis and Rowland - I didn't realise this was the script, makes sense now. I've run it (on dc2) and it gets as far as: need update: SRV _ldap._tcp.mysite._sites.ForestDnsZones.mydomain.org.uk dc2.mydomain.org.uk 389 [lots of updates needed] 10 DNS updates and 0 DNS deletes needed Successfully obtained Kerberos ticket to DNS/dc1.mydomain.org.uk as DC2$ and then it fails here:
2017 Nov 07
2
Samba 4.7 DC with BIND9_DLZ and MIT Kerberos fails at DNS Update
Dear all, a month ago I have filed bug #13066 about Samba 4.7 DC using BIND9_DLZ as DNS backend failing to run samba_dnsupdate using MIT Kerberos. The logs show a kerberos error "Request is a replay". Logs attached here: https://bugzilla.samba.org/show_bug.cgi?id=13066. Since I have not received any feedback on the bug report, I am trying this channel if someone has any idea how to fix
2016 Sep 23
5
dnsupdate_nameupdate_done - Failed DNS update
Hi, All 3 of my DCs regularly display an error in syslog almost exactly every 10 minutes. They have been doing this for quite some time, and I have so far ignored the message as everything else DNS-wise seemed to mostly be working - but I figured it was worth getting to the bottom of it if I can. So this isn't new at all but rather something that has been present for some time. I am using
2017 Dec 18
5
DHCP-DNS problems
On 18 December 2017 at 16:20, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > Even this looks wrong, I would expect something like this: > > Dec 18 07:43:59 dc3 dhcpd: DHCPREQUEST for 192.168.0.111 from > cc:4e:ec:e9:c8:d3 via eth0 > Dec 18 07:43:59 dc3 dhcpd: DHCPACK on 192.168.0.111 to cc:4e:ec:e9:c8:d3 > via eth0 > Dec 18 07:47:33 dc3 dhcpd:
2018 Aug 21
3
Samba 4.8.4 + BIND 9.9.4 - possibility of nonsecure DNS updates
> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made
2020 Sep 11
1
dnsvi and bind_dlz
we have our own dnsvi based on nsupdate. i have problems with dns names, that are exists on dc2 but not on dc1. its faster then alwasy use a windows gui :-D On 11.09.20 10:06, Rowland penny via samba wrote: > On 11/09/2020 08:31, basti via samba wrote: >> Hello is there a way to use dnsvi with samba bind_dlz? >> When i use this i get error update failed: NOTAUTH >> > I
2017 Sep 27
2
Samba as AD travails
Many (many) hours later, I'm finally throwing in the towel and seeking help. I have read everything I can find on the internet to no avail to get past my issues. I have to say, I'm very disappointed in the general quality and fragmentation of information on this topic. Samba isn't a turn-key solution as an AD by any stretch of the imagination. I've run the gamut so far with
2018 Dec 12
1
[Solved] GSSAPI/Kerberos authenticate with Dovecot
OK, for now it seem to work. Server: dovecot.my.fqdn.com Security: STARTTLS Auth: Kerberos/GSSAPI Possible Problems: - Keytabfile (samba-tool delegation show dovecot\$) ? - IP as Servername - SSL/TLS Port 993 ? Maybe someone can complete the wiki with thunderbird settings? P.S. Roland kinit -V5 DOVECOTUSER at MY.FQDN.COM did also work I use the samba wiki, dont know why only export 3
2020 Feb 27
4
New PTR records not visible
Ok, new test. Besides that i dont like the python errors shown, this still looks good. So i dont know.. See below, i can not make it error. for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do samba-tool dns add dc1.internal.dom.tld $x.249.10.in-addr.arpa 158 PTR host-test.extrazone.dom.tld ; done Record added successfully Record added successfully Record added successfully Record added
2020 Feb 27
5
New PTR records not visible
Ok, we might have found something here. I created a small script, see below, easy to adapt. So, after running this i see the same problem as in : https://bugzilla.samba.org/show_bug.cgi?id=14268 If i do it manualy everything works fine. But if i "past the commands or run the script" Then i see this problem.. So im thinking here, the speed of adding is creating somekind or
2016 Apr 02
1
Demote a working DC fails with uncaught exception
On 01/04/16 22:38, spindles7 wrote: > Hi Rowland, > Have tried your patch, and now the Demote succeeds: > > root at dc3:~# samba-tool domain demote -Uadministrator > Using dc1.microlynx.com as partner server for the demotion > Password for [MICROLYNX\administrator]: > Deactivating inbound replication > Asking partner server dc1.microlynx.com to synchronize from us >
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
On 31/07/2019 12:04, Stefan G. Weichinger via samba wrote: > Am 31.07.19 um 12:50 schrieb Rowland penny via samba: >> On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote: >>> Am 31.07.19 um 12:32 schrieb Rowland penny via samba: >>>> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: >>>>> "dc" was the old name a few years ago
2015 Dec 10
2
Authentication to Secondary Domain Controller initially fails when PDC is offline
On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>
2015 Dec 10
4
Authentication to Secondary Domain Controller initially fails when PDC is offline
On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN
2017 Apr 12
2
BIND DNS Reverse Update
there is the same problem. My setup is as follow: router (DHCP/Bind as forwarder dc1 and dc2) /etc/dhcpd.conf option domain-name-servers 192.168.30.2, 192.168.30.6; dc1 (192.168.30.2) / dc2 (192.168.30.6) are domain Controller with bind_dlz DNS, dc2 is update via axfr dc1 ist dns master and where I see the errors. client 192.168.30.175#55454: update 'samdom.example.com/IN' denied
2019 Aug 12
3
dns_tkey_gssnegotiate: TKEY is unacceptable
I installed a third DC today. Replication works find, but as systemctl status samba-ad-dc showed an error w.r.t. dnsupdate I was running samba_dnsupdate ?verbose. Below is the output. It looks like there are some missing DNS records, but what are potential causes of this error: dns_tkey_gssnegotiate: TKEY is unacceptable I already checked what?s listed @