Ich glaube ich habe aus versehen den Upgrade-Prozess zu früh abgedreht (neutstart/shutdown), daher die Probleme.
Glaubst du? Waren danach Pakate unkonfiguriert oder wie kommst du zu der Annahme?
Ich weis einfach nicht ob der Upgradevorgang beendet war. da ich keine Meldung bekommen habe. Im 1. Moment habe ich aber keine Probleme festgestellt, erst am nächsten Tag beim Neustart der Rechner war das Auflödungsproblem da.
Funktioniert denn die Replikation zwischden Master und Backup?
Ja ein neuer User oder Dnseintrag wird repliziert.
samba-tool drs showrepl
root@PDC:~# samba-tool drs showrepl
Default-First-Site-Name\PDC
DSA Options: 0x00000001
DSA object GUID: 1b893c9b-60ff-472c-a420-620d3520a67b
DSA invocationId: bfdd2975-45d8-4ca9-8e67-23406f1fd031
==== INBOUND NEIGHBORS ====
DC=ForestDnsZones,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ Sat Jun 24 18:54:14 2017 CEST was successful
0 consecutive failure(s).
Last success @ Sat Jun 24 18:54:14 2017 CEST
DC=DomainDnsZones,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ Sat Jun 24 18:54:14 2017 CEST was successful
0 consecutive failure(s).
Last success @ Sat Jun 24 18:54:14 2017 CEST
DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ Sat Jun 24 18:54:14 2017 CEST was successful
0 consecutive failure(s).
Last success @ Sat Jun 24 18:54:14 2017 CEST
CN=Schema,CN=Configuration,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ Sat Jun 24 18:54:14 2017 CEST was successful
0 consecutive failure(s).
Last success @ Sat Jun 24 18:54:14 2017 CEST
CN=Configuration,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ Sat Jun 24 18:54:15 2017 CEST was successful
0 consecutive failure(s).
Last success @ Sat Jun 24 18:54:15 2017 CEST
==== OUTBOUND NEIGHBORS ====
DC=ForestDnsZones,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=DomainDnsZones,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
CN=Schema,CN=Configuration,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
CN=Configuration,DC=bmss,DC=intern
Default-First-Site-Name\BDC via RPC
DSA object GUID: 89000e13-5e8d-4e3e-ad54-fd33b0583e4e
Last attempt @ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
==== KCC CONNECTION OBJECTS ====
Connection –
Connection name: 627cdcef-a4d0-4dff-9dc7-d9dd96666bf5
Enabled : TRUE
Server DNS name : bdc.bmss.intern
Server DN name : CN=NTDS Settings,CN=BDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bmss,DC=intern
TransportType: RPC
options: 0x00000001
Warning: No NC replicated for Connection!
Was bedeutet dieser Eintrag?
Was ist, wenn du den Master mit LDAP-Backend als DNS-Server nimmst?
root@PDC:~# ucr get dns/backend
samba4
ucr set dns/backend=‘ldap’
/etc/init.d/univention-bind restart —> Gibt’s nicht!
Lg Richie