search for: lookupzone

...entries, the last-mentioned site suggests to remove them by hand. Most of the containers in the DNS console have only duplicate entries for DC1/2, so no problem. However, 3 don't: (removed subfolder and client PC entries; sanitized, translated where necessary GR->EN) *DNS/DC2/Forward-Lookupzones/my.domain.de* Name Type Data Time stamp (identical to parent folder) Source of Authority (SOA) [3], dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 (identical to parent folder) Nameserver (NS) dc1.my.domain.de. Static (identical to parent folder) Hos...

.... Most of the containers in the DNS console have only >> duplicate entries for DC1/2, so no problem. However, 3 don't: >> >> >> (removed subfolder and client PC entries; sanitized, translated where >> necessary GR->EN) >> >> >> *DNS/DC2/Forward-Lookupzones/my.domain.de* >> >> Name Type Data Time stamp >> (identical to parent folder) Source of Authority (SOA) [3], >> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >> (identical to parent folder) Nameserver (NS) dc1.my.domain.de. &g...

...t;> duplicate entries for DC1/2, so no problem. However, 3 don't: >>>> >>>> >>>> (removed subfolder and client PC entries; sanitized, translated where >>>> necessary GR->EN) >>>> >>>> >>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>> >>>> Name Type Data Time stamp >>>> (identical to parent folder) Source of Authority (SOA) [3], >>>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >>>> (identical to parent folder)...

...s to > remove them by hand. Most of the containers in the DNS console have > only duplicate entries for DC1/2, so no problem. However, 3 don't: > > > (removed subfolder and client PC entries; sanitized, translated where > necessary GR->EN) > > > *DNS/DC2/Forward-Lookupzones/my.domain.de* > > Name Type Data Time stamp > (identical to parent folder) Source of Authority (SOA) [3], > dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 > (identical to parent folder) Nameserver (NS) dc1.my.domain.de. > Static >...

...t; remove them by hand. Most of the containers in the DNS console have > only > duplicate entries for DC1/2, so no problem. However, 3 don't: > > > (removed subfolder and client PC entries; sanitized, translated where > necessary GR->EN) > > > *DNS/DC2/Forward-Lookupzones/my.domain.de* > > Name Type Data Time stamp > (identical to parent folder) Source of Authority (SOA) [3], > dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 > (identical to parent folder) Nameserver (NS) dc1.my.domain.de. > Static >...

...gt;>>> >>>>>> >>>>>> (removed subfolder and client PC entries; sanitized, translated >>>>>> where >>>>>> necessary GR->EN) >>>>>> >>>>>> >>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>> >>>>>> Name Type Data Time stamp >>>>>> (identical to parent folder) Source of Authority (SOA) [3], >>>>>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >>>>...

...;>>>>>> (removed subfolder and client PC entries; sanitized, translated >>>>>>>> where >>>>>>>> necessary GR->EN) >>>>>>>> >>>>>>>> >>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>> >>>>>>>> Name Type Data Time stamp >>>>>>>> (identical to parent folder) Source of Authority (SOA) [3], >>>>>>>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10...

...lder and client PC entries; sanitized, >>>>>>>>>> translated where >>>>>>>>>> necessary GR->EN) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>>>> >>>>>>>>>> Name Type Data Time stamp >>>>>>>>>> (identical to parent folder) Source of Authority (SOA) >>>>>>>>>> [3], >>>>&g...

...DNS console have only >>> duplicate entries for DC1/2, so no problem. However, 3 don't: >>> >>> >>> (removed subfolder and client PC entries; sanitized, translated where >>> necessary GR->EN) >>> >>> >>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>> >>> Name Type Data Time stamp >>> (identical to parent folder) Source of Authority (SOA) [3], >>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >>> (identical to parent folder) Nameserver (NS)...

...the containers in the DNS console have >> only >> duplicate entries for DC1/2, so no problem. However, 3 don't: >> >> >> (removed subfolder and client PC entries; sanitized, translated where >> necessary GR->EN) >> >> >> *DNS/DC2/Forward-Lookupzones/my.domain.de* >> >> Name Type Data Time stamp >> (identical to parent folder) Source of Authority (SOA) [3], >> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >> (identical to parent folder) Nameserver (NS) dc1.my.domain.de. &g...

...the DNS entry in all the clients. Guess since than the dynamic DNS update wasn´t working anymore, so I tried to find out the reason. What I found is that the SOA record was pointing still to the none existing DC. After searching a little bit I was able to change the SOA record for our Forward-lookupzone and the first workstations have been registered in the DNS...till today not enough. But I was only able to change the SOA record for our first "samdom.example.com" zone. For the "_msdcs.samdom.example.com" zone it´s not possible. I use exactely the same syntax...no success....

...>>>>>>>>>>>> translated where >>>>>>>>>>>> necessary GR->EN) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>>>>>> >>>>>>>>>>>> Name Type Data Time stamp >>>>>>>>>>>> (identical to parent folder) Source of Authority >>>>>>>>>>>>...

...DC1/2, so no problem. However, 3 don't: >>>>> >>>>> >>>>> (removed subfolder and client PC entries; sanitized, translated where >>>>> necessary GR->EN) >>>>> >>>>> >>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>> >>>>> Name Type Data Time stamp >>>>> (identical to parent folder) Source of Authority (SOA) [3], >>>>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00 >>>>> (identic...

...>>>> >>>>>>> (removed subfolder and client PC entries; sanitized, translated >>>>>>> where >>>>>>> necessary GR->EN) >>>>>>> >>>>>>> >>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>> >>>>>>> Name Type Data Time stamp >>>>>>> (identical to parent folder) Source of Authority (SOA) [3], >>>>>>> dc1.my.domain.de., hostmaster.my.domain.de. ?28.?10.?2015 15:00:00...

...;> (removed subfolder and client PC entries; sanitized, >>>>>>>>> translated where >>>>>>>>> necessary GR->EN) >>>>>>>>> >>>>>>>>> >>>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>>> >>>>>>>>> Name Type Data Time stamp >>>>>>>>> (identical to parent folder) Source of Authority (SOA) [3], >>>>>>>>> dc1.my.domain.de., hostmaster.my.do...

...ntries; sanitized, >>>>>>>>>>> translated where >>>>>>>>>>> necessary GR->EN) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>>>>> >>>>>>>>>>> Name Type Data Time stamp >>>>>>>>>>> (identical to parent folder) Source of Authority (SOA) >>>>>>>>>>> [3], &g...

...>>>>>>>> translated where >>>>>>>>>>>>> necessary GR->EN) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *DNS/DC2/Forward-Lookupzones/my.domain.de* >>>>>>>>>>>>> >>>>>>>>>>>>> Name Type Data Time stamp >>>>>>>>>>>>> (identical to parent folder) Source of Authority >>>>>>>>>&...

...e owner of all roles is the new DC. Also with the following check for all roles everything is ok. ldbsearch --cross-ncs -H /var/lib/samba/private/sam.ldb -b "CN=Infrastructure,DC=domain,DC=university,DC=de" -s base fsmoroleowner The only thing I saw - there is an DNS-entry "Forward-Lookupzones->domain->_msdcs.domain->pdc->_tcp". Sounds like an entry for the PDC, and there is still the DC which owned the roles. Do I have to change this manually ? In a next step I will demote (and reinstall) the DC which owned the roles, maybe this solves any inconsistencies, in case the...

...ients. > Guess since than the dynamic DNS update wasn´t working anymore, so I > tried to find out the reason. > > What I found is that the SOA record was pointing still to the none > existing DC. After searching a little bit I was able to change the > SOA record for our Forward-lookupzone and the first workstations have > been registered in the DNS...till today not enough. > > But I was only able to change the SOA record for our first > "samdom.example.com" zone. For the "_msdcs.samdom.example.com" zone > it´s not possible. I use exactely the sam...

...the new DC. > > Also with the following check for all roles everything is ok. > ldbsearch --cross-ncs -H /var/lib/samba/private/sam.ldb -b "CN=Infrastructure,DC=domain,DC=university,DC=de" -s base fsmoroleowner > > The only thing I saw - there is an DNS-entry "Forward-Lookupzones->domain->_msdcs.domain->pdc->_tcp". > Sounds like an entry for the PDC, and there is still the DC which owned the roles. > Do I have to change this manually ? > > In a next step I will demote (and reinstall) the DC which owned the roles, maybe this solves any inconsist...