similar to: adjust SOA record

Hi all, I am experiencing strange behaviour regarding DNS resolution with my samba-driven AD. This is with Debian-packaged samba on raspberry Pi: # samba -V Version 4.19.5-Debian # uname -a Linux dc3.ad.mydomain.tld 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux I would expect that every DNS server of the domain would respond with the same SOA record. But

Hey, Thank you Louis for this script, I didn't yet took time to dig in but I'll do. I didn't took time neither to perform another test. That should be done today. Anyway I waited for DC synchronisation before posting. I joined my DC and removed the old ones almost at same time then I gave more than 12 hours to my DC to synchronize. Then I tried to understand what happened, I wrote

Le 27/05/2019 à 09:50, Rowland penny via samba a écrit : > On 27/05/2019 08:28, Julien TEHERY via samba wrote: >> Hi >> >> I have a setup with 2 DC on a main site, et 14 DCs which are located >> on 7 AD sites. >> I recently noticed in my DNS zones that my SOA record is associated >> to the last DC that was joined to the domain. >> But this DC is

Hi Ole, I'm still not answering your issue but I come back to speak about TTL. Perhaps someone would be able to bring us some light on that. This morning I'm trying to reproduce the way I do broke my test AD domain. This leads me to deal with SOA record (I broke my test AD seizing FSMO roles before removing old FSMO owner, SOA was not changed during that process and I suspect this was

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

[root at smb4-1 ~ (master)]# samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca ALL -U administrator Password for [BROCKLEY\administrator]: Name=, Records=4, Children=0 SOA: serial=3, refresh=900, retry=600, expire=86400, minttl=3600, ns=SMB4-1.brockley.harte-lyne.ca., email=hostmaster.brockley.harte-lyne.ca. (flags=600000f0, serial=110, ttl=3600) NS:

Hello Rowland, ldbsearch command is returning 0 records. # returned 0 records # 0 entries # 0 referrals On the backup front, I take the back up using samba-tool backup command and it was successful. Can I create a new ForestZone using samba-tool? I asking this question as RSAT is not connecting to DNS server. Thanks & Regards, Anantha Raghava H A This e-mail communication and any

Back from another test: rather than build new DCs, join them and use one of them to seize FSMO roles, I just seize FSMO with one of my current DCs. Once more the SOA was not updated, which seems to mean there is a real issue about that as seizing these roles has chances to precede removal of old FSMO owner. To update SOA record using samba-tool: 1) If not created, create a NS record for the DC

On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: >> Hi Ole, >> >> I'm still not answering your issue but I come back to speak about >> TTL. Perhaps someone would be able to bring us some light on that. >> >> This morning I'm trying to reproduce the way I do broke my test AD >> domain. This

On 11/20/2015 10:17 AM, mathias dufresne wrote: > > > 2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com > <mailto:lingpanda101 at gmail.com>>: > > On 11/20/2015 7:40 AM, Ole Traupe wrote: > > > > Am 20.11.2015 um 11:54 schrieb mathias dufresne: > > Hi Ole, > > I'm still not answering your issue

Hi I have a setup with 2 DC on a main site, et 14 DCs which are located on 7 AD sites. I recently noticed in my DNS zones that my SOA record is associated to the last DC that was joined to the domain. But this DC is located on one of the remote sites. Is this behavior normal or would it be better if I updated this record via "samba-tool dns update" to point it to one of my 3 main

Ok, I see. Nevertheless, thank you very much for your effort! I must say that I can't actually believe that no one knows an answer to this problem. It must affect MANY people using Samba DCs. According to all the tests on the wiki, everything is working fine. Then I pull the plug on my first DC and no one can log on. And this time I waited far longer than the suggested "refresh

On 27/05/2019 09:12, Julien TEHERY via samba wrote: > Le 27/05/2019 à 09:50, Rowland penny via samba a écrit : >> On 27/05/2019 08:28, Julien TEHERY via samba wrote: >>> Hi >>> >>> I have a setup with 2 DC on a main site, et 14 DCs which are located >>> on 7 AD sites. >>> I recently noticed in my DNS zones that my SOA record is associated

Hi, How can the SOA record of a domain be changed? I need to decrease expire and minttl Thanks. -- P?ter Varkoly Greuleinweg 37. D-90411 N?rnberg

2015-11-20 15:11 GMT+01:00 James <lingpanda101 at gmail.com>: > On 11/20/2015 7:40 AM, Ole Traupe wrote: > >> >> >> Am 20.11.2015 um 11:54 schrieb mathias dufresne: >> >>> Hi Ole, >>> >>> I'm still not answering your issue but I come back to speak about TTL. >>> Perhaps someone would be able to bring us some light on

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,

On 11/26/2015 10:35 AM, Ole Traupe wrote: > >>> ANYWAYS, I would like to approach from a different direction: >>> >>> If my first DC is offline, a ping on any of my domain machines takes >>> 5+ seconds to resolve. I figure that my logon problems reflect >>> multiple such timeouts during the logon process accumulating to a >>> total

Am 20.11.2015 um 11:54 schrieb mathias dufresne: > Hi Ole, > > I'm still not answering your issue but I come back to speak about TTL. > Perhaps someone would be able to bring us some light on that. > > This morning I'm trying to reproduce the way I do broke my test AD > domain. This leads me to deal with SOA record (I broke my test AD > seizing FSMO roles before

Although I don't know what "dig" actually means, I was able to dig up the following for my SOA: my.domain.tld. 3600 IN SOA DC2.my.domain.tld. hostmaster.my.domain.tld. 29 180 600 86400 180 This is after I reduced refresh interval and minimum TTL to 3 min (180 s). Still, the TTL of the SOA itself is 1h (3600 s). This strongly suggests, that the TTL for DNS info

Hi. I'm running Sernet Samba 4.7 on Ubuntu 16. I noticed that when my first DC went away, I had problems. The SOA record for the domain still points at that first DC. I found, in this entry from 2014 ( https://lists.samba.org/archive/samba/2014-August/184301.html) that "Windows AD servers actually 'lie' about the SOA record, and always say that it points to themselves. So in a