similar to: DNS forwarders are not replicated

I joined a Samba server to a Windows 2003 server. As far as I can see, replication works, but sometimes there are errors like this: ; TSIG error with server: tsig verify failure Failed nsupdate: 2 update (nsupdate): SRV _ldap._tcp.Default-First-Site- Name._sites.ForestDnsZones.domain.local server03.domain.local 389 Calling nsupdate for SRV _ldap._tcp.Default-First-Site-

I had configured Samba AD's with Bind9_DLZ in all DC. But for some reason (i couldn't determine) three (sambadc02,03,04) AD's responded very slowly . So change to Samba_Internal backend into the servers with problem and works fine. sambadc01 -> with FSMO roles - Bind9_DLZ sambadc02 -> Samba_Internal sambadc03 -> Samba_Internal sambadc04 -> Samba_Internal My question is:

Aaaaaaand more problems... Welcome to the continuing saga of FILER. It appears that neither SOA or NS records were updated during the process of moving fsmo roles to CBADC01. SOA entries on all three active DCs point to FILER. There aren't any NS records for any of the new DCs, only FILER. In RSAT each DNS server's properties show filer.cb.cliffbells.com is the primary server. This

Hi Anantha, > The upgrade from 4.6.5 broke all the servers. Although the services were > running and there is no error message, DNS resolution failed. Even from > inside the domain controllers, DNS queries failed. > > Samba Version 4.7.1 and Named Version 9.9.4. The same issue happened > with samba version 4.7.3 and 4.7.4 > > We had to revert back to 4.6.5 to bring the

Hai eveyone.   I know about the dns "things" in the past. DNS Islanding problems etc. This one is a bit hijacking the subject : “Horrible BIND9_DLZ DNS breakage after DC replaced and samba-tool domain demote --remove-other-dead-server”     I would like to suggest a smale change in how we suggest to setup samba ADDC dns things, and i do think this help in the setup of the AD

Hi, I've spent the last days building the Samba4 RC1 and trying to move a DC from 2003 to Samba4. I've followed the HowTo's, first to build Samba4, and then to add a domain as a backup domain controller on the Wiki. Everything seems to be working fine. My backup domain controller gets all the information from the PDC, this is LDAP, Kerberos and DNS. As suggested by a message on this

I've setup a script that scan non-disabled user base, base query: (&(objectClass=user)(!(objectClass=computer))(!(userAccountControl:1.2.840.113556.1.4.803:=2))) and for every user i check the 'last password change' data value, doing some thing (eg, disabling it ;-) if it is too far. I've found that my script get also some 'dns-*' account; looking at data i've

Hello, i have an issue with existing installation of samba4 domain controller that is specific to dns managment. In the domain I have two samba4 4.0.7 and one windows 2003 server that I plug periodically to manage the dns. All fsmo roles are transfered to samba. All aspects of the domain work perfectly, except one, the samba-tool dns commands do not work. All commands when executed on samba

We've added an extra DC for redundancy to the Debian based Active Directory. We updated our older smaba version to the current one, and joined a new DC. Then the commands where givven to move all the FSMO roles Which we verified with "samba-tool fsmo show", which showed that all roles are on the new DC. However in DNS all underscore srv records of the AD services still point to the

Hi, While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a peculiar problem. AD Component is up, but DNS is just not coming up. kinit is reporting KDC not found problem. All these years I have been compiling samba from source and for nearly 7 years, it was working like a charm. But this upgrade activity, we ran into rough weather. We do not upgrade the existing servers where as,

Hi! The problem with this is that both Dcs will continue on the network ... I wanted to transfer the FSMOs, because in DC (that has today) I will perform an S.O. upgrade and if something goes wrong, it is already correct !!! Regards; On 06-06-2018 11:05, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 10:46:48 -0300 > Carlos via samba <samba at lists.samba.org> wrote: >

To get the question of why new servers, this one I'm using has hardware whose remaining life is measured in days. The elastic bands and sticky tape it is held together with won't hold for much longer. I'm using it to build and test a new environment, but then I need to migrate that onto something with a little more vitality before bringing it into production (in the next 56 hours). As

On 22/03/2023 01:04, Anantha Raghava via samba wrote: > Hi, > > While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a > peculiar problem. AD Component is up, but DNS is just not coming up. > kinit is reporting KDC not found problem. > > All these years I have been compiling samba from source and for nearly 7 > years, it was working like a charm. But this

Hi! In wiki -> https://wiki.samba.org/index.php/Transferring_and_Seizing_FSMO_Roles#Difference_of_Transferring_and_Seizing_FSMO_Roles "If the DC is broken (e. g. hardware defect) and will never come back again, then you can seize the role on a remaining DC. It is very important that the old DC will never be connected to the network again, if it is connected again, this will cause

Hi, Last evening we upgraded one of our 4 Domain Controllers from 4.6.5 to 4.7.1 and all of a sudden the DNS resolution issue started. We are using BIND9_DLZ back end. This server we had upgraded has all 7 FSMO Roles. Some time back we upgraded the other 3 servers from version 4.6.5 to 4.7.1 and there was no issue at all. I have also observed a very peculiar behaviour that is all of a

>> Does this apply if, instead of an upgrade, one provisions a new DC >> on, say, 4.9 and joins it? In short, will this allow you to get your >> DCs to 4.9 by creating new DC's on 4.9, and then demote/remove all >> the 4.7 DC's after the new 4.9 DC's are synced etc? RPvs> I do not know, I personally never tried it, but even if it does work, RPvs> it

Hello, I am in the process of upgrading one single DC (internal DNS) to 4.8.12. I have followed the procedure of adding a new DC, transfert FSMO roles and demote the old DC. Everything gone right (except at the tranfert FSMO step where I faced the problem described here https://lists.samba.org/archive/samba/2017-August/210140.html , this bug subsists in 4.8.12 , maybe it has been fixed in later

On 23/03/23 5:08 pm, Rowland Penny via samba wrote: > > > On 23/03/2023 11:30, Anantha Raghava via samba wrote: > >> You are right. They are not starting. One of the server is throwing >> NTDS and rid related error and exit. By the way this one was having >> all FSMO roles before it was removed. I haven't tried the other one. >> I will try and & turn

Hi all, Playing with delegation today we delegated rights to some user on some OU and its contents for it can modify users inside that OU and children. We used "advanced view" in ADUC then "properties" on our delegated OU, then "security" tab, and finally we gave rights to our user. Perhaps this process is not correct but we believe it is a valid process to delegate

So not the problem of using "seize" when both the OLD-FSMO server and NOVO-FSMo are active and on the network? The problem is to use "seize" if OLD-FSMO is not on the network and then come back? If I understood how it would be .... Regards; On 06-06-2018 15:46, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 15:35:29 -0300 > Carlos via samba <samba at