search for: microsoftdns

...estDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://artemis] 'CN=LostAndFound,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://aquarius] Attributes found only in ldap://artemis: cn Attributes found only in ldap://aquarius: CN FAILED Comparing: 'CN=MicrosoftDNS,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://artemis] 'CN=MicrosoftDNS,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://aquarius] Attributes found only in ldap://artemis: cn Attributes found only in ldap://aquarius: CN FAILED Comparing: &...

...earch --cross-ncs --show-binary -H > /usr/local/samba/private/sam.ldb -b dc=omtn,dc=de -s sub > '(&(objectclass=dnsNode)(name=*))' > ~/addns > > oot at OMTNDC8:~# grep dn: ~/addns | grep DNS | grep "_ms" > dn: > DC=_kerberos._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de > dn: > DC=_ldap._tcp....

On 29/04/2020 10:58, Olaf Dreyer via samba-technical wrote: > > I run a setup with two Samba DC (currently samba 4.12.2 on debian 10 > VMs). I started with a Windows 2003 DC but the last Windows DC has > been removed a few years ago from this setup. this is really the wrong list for this, so i have CC'ed the samba mailing list, please reply there. You say you started with Win

...ap://artemis] > 'CN=LostAndFound,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' > [ldap://aquarius] > Attributes found only in ldap://artemis: > cn > Attributes found only in ldap://aquarius: > CN > FAILED > > Comparing: > 'CN=MicrosoftDNS,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' > [ldap://artemis] > 'CN=MicrosoftDNS,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' > [ldap://aquarius] > Attributes found only in ldap://artemis: > cn > Attributes found only in ldap://aquarius: >...

.../samba/private/sam.ldb -b dc=omtn,dc=de -s sub > > > '(&(objectclass=dnsNode)(name=*))' > ~/addns > > > > > > oot at OMTNDC8:~# grep dn: ~/addns | grep DNS | grep "_ms" > > > dn: > > > DC=_kerberos._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestD > > > nsZones,DC=omtn,DC=de > > > dn: > > > DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZo > > > nes,DC=omtn,DC=de > > > dn: > > > DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625- > > > 5b7d8a36f903.domains._msdcs,...

> > Good, the _msdcs domain is the forest domain So is it normal that DC4 is not in that? > but are there records for all three DCs in: > > DC=your.domain.com > ,CN=MicrosoftDNS,DC=DomainDnsZones,DC=your,DC=domain,DC=com > I tried to find this path in the LDAP Browser and ASDI Edit but I did not manage in find it. In the Windows DNS Manager connected to DC1 I found _ldap SRV records for dc1 and dc2 into DNS\dc1\Forward Lookup Zones\my.domain.com \domaindnszones\_sites\...

...-binary -H >> /usr/local/samba/private/sam.ldb -b dc=omtn,dc=de -s sub >> '(&(objectclass=dnsNode)(name=*))' > ~/addns >> >> oot at OMTNDC8:~# grep dn: ~/addns | grep DNS | grep "_ms" >> dn: >> DC=_kerberos._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn: >> DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de >> dn:...

...>>> 2. Why can't I query and/or delete it using standard means? >>> Probably because it is a wrong record ???? >>> Try running this on a DC: >>> ldbsearch --cross-ncs --show-binary -H /var/lib/samba/private/sam.ldb -b >>> 'DC=_msdcs.domain.com,CN=MicrosoftDNS,DC=ForestDnsZones,DC=domain,DC=com' >>> -s sub '(objectClass=dnsNode)' >> Thanks, Rowland. I've just tried your command but the output does not contain >> that bogus record. I even tried to remove the objectClass filter - still no >> luck. > One...

...nny: > On 17/12/15 13:54, Ole Traupe wrote: >> Rowland, thank you, but before we do that: >> >> - what now with the 'gc' record? 2nd DC yes or no? > > Which one ? I have these: > > dn: > DC=_gc._tcp.Default-First-Site-Name._sites,DC=samdom.example.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=samdom,DC=example,DC=com > > dn: > DC=_gc._tcp,DC=samdom.example.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=samdom,DC=example,DC=com > > dn: > DC=_ldap._tcp.gc,DC=_msdcs.samdom.example.com,CN=MicrosoftDNS,DC=ForestDnsZones,DC=samdom,DC=example,DC=com > >...

...ldb /usr/local/samba/bin/ldbsearch --cross-ncs --show-binary -H /usr/local/samba/private/sam.ldb -b dc=omtn,dc=de -s sub '(&(objectclass=dnsNode)(name=*))' > ~/addns oot at OMTNDC8:~# grep dn: ~/addns | grep DNS | grep "_ms" dn: DC=_kerberos._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625-5b7d8a36f903.domains._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZones,DC=omtn,DC=de dn: DC=_ldap._tcp.CorporateDataCenter._sites.gc....

...private/sam.ldb -b dc=omtn,dc=de -s sub >>>> '(&(objectclass=dnsNode)(name=*))' > ~/addns >>>> >>>> oot at OMTNDC8:~# grep dn: ~/addns | grep DNS | grep "_ms" >>>> dn: >>>> DC=_kerberos._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestD >>>> nsZones,DC=omtn,DC=de >>>> dn: >>>> DC=_ldap._tcp.dc._msdcs,DC=omtn.de,CN=MicrosoftDNS,DC=ForestDnsZo >>>> nes,DC=omtn,DC=de >>>> dn: >>>> DC=_ldap._tcp.b66950c4-e9b8-4bc9-b625- >>>> 5b7d8a36f903.dom...

On 17/11/2020 16:19, Mani Wieser via samba wrote: > ldbdel is definitely not the right tool: it will delete both records > > lddsearch: returned 2 records, because the dn is exactly the same Didn't think you could have two records with the same DN, if this is true, then it does sound like a bug, care to share the two DN's ? Rowland

> I think it would be easier to: > > ldbedit -e nano -H /var/lib/samba/private/sam.ldb --cross-ncs -b > "DC=1.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=samdom,DC=com" > "(DC=21)" > > On a DC. > > Rowland Well, not so simple... I tried ldbedit -e vim -H /usr/local/samba/private/sam.ldb --cross-ncs -b "DC=91,DC=41.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=home,DC=serbe,DC=...

...anquil,DC=it (and any child objects) updating test.tranquil.it keeping 6 values, removing 1 values updating ForestDnsZones.test.tranquil.it keeping 2 values, removing 1 values updating DomainDnsZones.test.tranquil.it keeping 2 values, removing 1 values updating DC=67,DC=149.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=test,DC=tranquil,DC=it keeping 0 values, removing 1 values updating DC=@,DC=149.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=test,DC=tranquil,DC=it keeping 2 values, removing 1 values updating DC=@,DC=151.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,D...

...; Samba Team > http://samba.org > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba Startup time of bind is also very slow: Dec 3 20:10:06 srv named[20349]: samba_dlz: trying container 'CN=MicrosoftDNS,CN=System,DC=test,DC=intern' Dec 3 20:10:10 srv named[20349]: samba_dlz: configured writeable zone '110.168.192.in-addr.arpa' Dec 3 20:10:10 srv named[20349]: samba_dlz: trying container 'CN=MicrosoftDNS,CN=System,DC=test,DC=intern' Dec 3 20:10:14 srv named[20349]: samba_dlz:...

...ONFIGURATION]: SUCCESS > > * Comparing [SCHEMA] context... > > * Objects to be compared: 1561 > > * Result for [SCHEMA]: SUCCESS > > * Comparing [DNSDOMAIN] context... > > * Objects to be compared: 115 > > Comparing: > 'DC=251,DC=13.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=domain,DC=de' > [ldap://location-000001.domain.de] > 'DC=251,DC=13.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=domain,DC=de' > [ldap://location-000002.domain.de] > Difference in attribute values: > dnsRecord => > ['...

Hello, I've just discovered a bogus record in _msdcs zone which exists on samba-dc (vm-dc4, 4.12.2) only and missing on a PDC (vm-dc1, Windows Server 2008 R2): # samba-tool dns query localhost _msdcs.domain.com @ ALL -U administrator 2>/dev/null Password for [DOMAIN\administrator]: Name=, Records=3, Children=0 NS: vm-dc1.domain.com. (flags=600000f0, serial=181, ttl=3600)

On 30/04/2020 11:44, Olaf Dreyer wrote: > Hi, > > I restored the last backup with the 4.11.6 setup. This is working fine > and i can confirm that my AD is set up with a single forwarding zone, > there is no _msdsc zone. On this 4.11.6 setup also the Windows DNS > Tool does not complain. When upgrading to 4.12.2 DNS administration > fails again with

...??? msDS-HasDomainNCs ??? msDS-SDReferenceDomain ??? hasPartialReplicaNCs ??? nCName * Comparing [SCHEMA] context... * Objects to be compared: 2621 * Result for [SCHEMA]: SUCCESS * Comparing [DNSDOMAIN] context... * Objects to be compared: 46 Comparing: 'DC=@,DC=filial1.company.local,CN=MicrosoftDNS,DC=DomainDnsZones,DC=filial1,DC=company,DC=local' [ldap://localhost] 'DC=@,DC=filial1.company.local,CN=MicrosoftDNS,DC=DomainDnsZones,DC=filial1,DC=company,DC=local' [ldap://dc02] ??? Difference in attribute values: ??????? dnsRecord => ['\x04\x00\x01\x00\x05\xf0\x00\x00:\x00\x00...

...bjects) > updating test.tranquil.it keeping 6 values, removing 1 values > updating ForestDnsZones.test.tranquil.it keeping 2 values, removing 1 > values > updating DomainDnsZones.test.tranquil.it keeping 2 values, removing 1 > values > updating DC=67,DC=149.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > nsZones,DC=test,DC=tranquil,DC=it keeping 0 values, removing 1 values > updating DC=@,DC=149.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDn > sZones,DC=test,DC=tranquil,DC=it keeping 2 values, removing 1 values > updating DC=@,DC=151.168.192.in-addr.arpa,CN=MicrosoftDNS,D...