similar to: samba 4.12.2: WERR_DNS_ERROR_DS_UNAVAILABLE, unable to manage samba DNS

On 29/04/2020 17:29, Olaf Dreyer wrote: > Hi Rowland, > > this is a good question. Does this listing help or answer? > > root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al > total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de > drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . > drwx------ 7 root root????? 4096 Apr 29 11:25 .. > -rw------- 1 root staff

G'Day Olaf, If this was working before, then it would be this bug: https://bugzilla.samba.org/show_bug.cgi?id=14310 I'm a bit swamped right now, per Microsoft the correct fix is for our DNS Management server to ignore these values. Can you see if your error looks like this in the server logs? Andrew Bartlett On Wed, 2020-04-29 at 18:53 +0200, Olaf Dreyer via samba wrote: > Well,

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

Hi Rowland, this is a good question. Does this listing help or answer? root at OMTNDC3:/usr/local/samba/private/sam.ldb.d# ls -al total 93220 Node,CN=Schema,CN=Configuration,DC=omtn,DC=de drwxr-x--- 2 root bind????? 4096 Apr 28 16:03 . drwx------ 7 root root????? 4096 Apr 29 11:25 .. -rw------- 1 root staff 30384128 Apr 29 12:46 'CN=CONFIGURATION,DC=OMTN,DC=DE.ldb' -rw------- 1 root

Well, sometimes I? feel really old..... The last dynamic changes in DNS where made earlier this month, probably before I upgraded from 4.11.5 to newer version. With samba 4.11.5 DNS administration using samba-tool was working fine. Do you think this old setup is the reason for the problems?Any way to fix it? Best regards, Olaf Am 29.04.2020 um 18:35 schrieb Rowland penny via samba: > On

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 WERR_DNS_ERROR_DS_UNAVAILABLE. I will try the steps described in the MS document? and come back

Hi, Well, I joined a new DC on my domain and when run "ldapcmp" it reported errors. I follow Samba wiki to Joining a Samba to an Existing Active Directory. * Comparing [DNSFOREST] context... * Objects to be compared: 18 Comparing: 'CN=Infrastructure,DC=ForestDnsZones,DC=dom,DC=city10,DC=com,DC=br' [ldap://artemis]

> > 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

Am 17.12.2015 um 15:33 schrieb Rowland penny: > 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

Rowland, thank you, but before we do that: - what now with the 'gc' record? 2nd DC yes or no? - if you say that the internal DNS is not compatible with a multi-DC setting, than we can stop here, no? Ole Am 17.12.2015 um 14:32 schrieb Rowland penny: > On 17/12/15 12:50, Ole Traupe wrote: >> >> I somehow doubt that. Still it seems that no one here has an idea of >>

Hi Denis & Rowland Thanks for the suggestion to trim the smb.conf after which the DC-1 is connecting to the Windows Server 2008 shared folder smbclient -k //IUMSVRAPP01/Pastel12 -d 9 and DC-2 is also connecting after using the DNS name of the Windows server. *You'd better switch your DNS to Bind-DLZ. Internal DNS is not that good for larger site (looking at your DNS domain name, I guess

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)

Hi Denis I have upgraded my samba DC-1 from 4.6.12 to 4.7.4 which has solved the replication issues between DC-1 and DC-2. Now both the DC's are running on 4.7.4. Like Rowland said previously, you should remove all RODC that have been installed prior to Samba 4.7. There are many fixes that have been added since 4.6. Before I remove my RODC's I like to clear out few doubts: 1. Instead of

Hi I have multi domain environment with root domain and subdomain. Forest and domain level windows 2003 native. Also forest prep and domain prep did for sccm 2007 ocs 2007 and Exchange 2003. After join Samba to domain like ad dc I had some problem with replication: ################################################# [root at dc03 ~]# samba-tool drs replicate dc02 dc03

Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there):   Name=, Records=3, Children=0     SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600,

Am 17.12.2015 um 16:10 schrieb Rowland penny: > On 17/12/15 14:56, Ole Traupe wrote: >> >> >> Am 17.12.2015 um 15:33 schrieb Rowland penny: >>> 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

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

On 18/05/2020 18:27, Alex wrote: >>>> 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'

Hi, I'm trying to remove a DC from a site we have shutdown. The demote command is throwing up this message: [root at aragorn ~]# samba-tool domain demote --remove-other-dead-server=pippin Removing nTDSConnection: CN=eca08dbb-1f34-476e-96dd-33ec22b2bc94,CN=NTDS Settings,CN=GANDALF,CN=Servers,CN=SAOPAULO,CN=Sites,CN=Configuration,DC=e-trust,DC=com,DC=br Removing nTDSDSA: CN=NTDS

> 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