similar to: bogus record in _msdcs zone in samba-dc

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'

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,

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

On Sun, Sep 22, 2019 at 7:19 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 22/09/2019 13:08, Christopher Wooley wrote: > > I used the distro's compilation, samba -V : Version 4.7.6-Ubuntu, but > > I think it's already running DLZ. I know I recompiled Bind9 in order > > to add the DLZ necessary flags. > Then you were wasting your time,

On 11/02/2020 16:29, Alex via samba wrote: > Rowland, > > After some debugging, I was able to find the source of this error: > ERROR(runtime): uncaught exception - (9003, 'WERR_DNS_ERROR_RCODE_NAME_ERROR') > > It's thrown during the join b/c Samba is trying to find the DNS record for the > new DC (the Samba) inside DC=DomainDnsZones,DC=domain,DC=com

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

Replaced as instructed and ran the command. It claimed "success", however (RSAT) DNS Manager still shows demoted DC as SOA record. BTW, this demoted DC is now shut off. Suggestions? > Run this on a DC: > > samba-tool dns delete 127.0.0.1 samdom.example.com @ NS fqdn_string -U > Administrator > > Replace: 'samdom.example.com' with your dns domain name. >

On 07/30/2019 09:15 AM, Rowland penny via samba wrote: > This is getting weird, anything and everything seems to be working > except for Serverinfo ??????? The other DC is Windows Server 2003, does that make any difference? Adding a DNS entry also fails: athena:~# samba-tool dns add athena edm-inc.com smtp A 10.10.1.9 ERROR(runtime): uncaught exception - (9717,

On Sun, 10 May 2015, Rowland Penny wrote: > can you post your named conf files. Sure. This is samba's: dlz "AD DNS Zone" { database "dlopen /mnt/domain/samba/europa/lib/bind9/dlz_bind9_9.so"; }; and this is BIND's (notice the last line commented out): options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db";

On 07/30/2019 10:05 AM, Rowland penny via samba wrote: > > Try running these commands: > > ldbsearch --cross-ncs --show-binary -H /var/lib/samba/private/sam.ldb > -b 'CN=MicrosoftDNS,DC=DomainDnsZones,DC=edm-inc,DC=com' -s sub > '(objectclass=dnsNode)' > domain_records.ldif > > ldbsearch --cross-ncs --show-binary -H /var/lib/samba/private/sam.ldb >

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

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

>>> The other option is to remove 'DC=DomainDnsZones,DC=domain,DC=com' and >>> 'DC=ForestDnsZones,DC=domain,DC=com' after the join and then run >>> 'samba_upgradedns', would this work ? >> While it seems to be safe to delete DomainDnsZones context, the ForestDnsZones >> context seems to contain the real DNS zone info: > First and

On 27/11/15 15:24, mathias dufresne wrote: > > > 2015-11-27 15:49 GMT+01:00 Rowland Penny <rowlandpenny241155 at gmail.com > <mailto:rowlandpenny241155 at gmail.com>>: > > On 27/11/15 14:30, James wrote: > > On 11/27/2015 9:16 AM, Rowland Penny wrote: > > On 27/11/15 13:23, James wrote: > > On 11/26/2015 11:12

On 2016-11-04 11:31, Rowland Penny via samba wrote: > <<<<< cut >>>>>>>> > >> root at dtdc03:~# samba-tool dns zonelist dtdc03 >> 3 zone(s) found >> >> pszZoneName : xxx.168.192.in-appr.arpa >> Flags : DNS_RPC_ZONE_DSINTEGRATED >> DNS_RPC_ZONE_UPDATE_SECURE >> ZoneType

Hi, I have three Samba Domain Controllers, two in the LAN local network (dc1 and dc2) and one in a remote network which is accessible from the LAN through a VPN connection (dc4). Every domain controller can reach every other domain controllers, and every type of traffic is permitted by firewalls, they can ping and access to every TCP and UDP ports. Checking the Samba replication I see that the

Il giorno mar 17 dic 2019 alle ore 17:49 Rowland penny via samba < samba at lists.samba.org> ha scritto: In the last year this has come up a few times, try reading this > > https://support.microsoft.com/en-gb/help/817470/how-to-reconfigure-an-msdcs-subdomain-to-a-forest-wide-dns-application > It looks like we need a tool to correct AD :-( > Thanks! I will read that article. Do

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

Hi, After joining samba DC (vm-dc4) to MS AD, I've discovered that most DNS entries were not populated. Below are the only entries in the AD for the new DC: domain.com:VM-DC4 900 A 172.26.1.84 _msdcs.domain.com:d14c4206-79e3-441f-868a-6c693415256a 900 CNAME vm-dc4.domain.com. Please, help me figure out what's going on. Here is the excerpt from log.samba:

2016-02-29 0:05 GMT+01:00 Reindl Harald <h.reindl at thelounge.net>: > > > Am 28.02.2016 um 23:54 schrieb Rowland penny: > >> On 28/02/16 22:42, Reindl Harald wrote: >> >>> >>> >>> Am 28.02.2016 um 23:10 schrieb Rowland penny: >>> >>>> On 28/02/16 21:56, Reindl Harald wrote: >>>> >>>>>