similar to: Replacing one of my Samba DCs

I have been trying to figure out this problem for a couple weeks no with no luck. Out of the blue, I started getting TSIG errors on my Samba AD DC. I pulled the logging extract below after turning up the log level to 10 and waiting for a reoccurrence. These errors will typically happen every few hours with one to three occurrences withing the same second. Can anybody tell from this what Samba is

Default Domain Controller Policy and Default Domain Policy have been deleted/lost at some unknown time. How do I clean this up? Just delete these or can I recreate somehow? In cleaning up my pair of Samba AD DCs, I was validating access to GPOs and discovered that while my more recent custom GPSs are fine, the GPOs for Default Domain Controller Policy and Default Domain Policy are not. When

I recently upgraded my Samba Domain Member server that provides a share for Windows clients to write their backups to. The backup clients use an AD credential to connect to the share, so individuals are not connecting to the share. This works well and has for years. However, when I upgraded to Samba v4.21.3 (built from source, same distro as my Samba AD DCs), I started getting my logs cluttered up

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

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

Rowland, thank You, but this removes only the NS record, but the faulty domain A records remain. How to deal with them, I don't know. They behave unlike the ordinary A records. Name=, Records=8, Children=0     SOA: serial=27, refresh=900, retry=600, expire=86400, minttl=3600, ns=blacktux.interbronz.local., email=hostmaster.interbronz.local. (flags=600000f0, serial=27, ttl=3600)     NS:

Dear R Developers, After having fully read "Advanced R First Edition" , and having just bought my physical copy of "Advanced R Second Edition", I recommend that: Any community member interested in the development of R reads "Advanced R Second Edition", which explains R Language Core concepts cristal clear, and shows the motivation behind libraries such as

Excellent suggestion! I forgot about that. I get: # smbd -b | egrep "LOCKDIR|STATEDIR|CACHEDIR|PRIVATE_DIR" LOCKDIR: /var/cache/samba STATEDIR: /var/lib/samba CACHEDIR: /var/cache/samba PRIVATE_DIR: /var/lib/samba/private In my response to Roland I figured using --prefix /var/lib/samba That looks correct, right? I don't suppose the /var/cache directories figure into

I downloaded it yesterday,first stuck by the login name and password in its admin page,there is no place in the document mentioned the password.It took me half hour to google,finally found the login name is maint,felt quite frustrated,why they lost such important info.? then I added some accounts according to the instruction ,seemed quite easy.again ,encountered several problems unsolved after

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,

For some reason, the provision picked up 2 network IP addresses in my VM. Snipped output below... root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 dwVersion : 0xece0205 fBootMethod : DNS_BOOT_METHOD_DIRECTORY fAdminConfigured : FALSE fAllowUpdate : TRUE fDsAvailable : TRUE

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

Dear R listers, When using smooth.spline to interpolate data, results are generally good. However, some cases produce totally unreasonable results. The data are values of pressure, temperature, and salinity from a probe that is lowered into the ocean, and the objective is to interpolate temperature and salinity to specified pressures. While smooth.spline provides excellent values at the

Due to a mistake I created a subdomain with the name of the domain itself. In my case the domain is briesebaer.intern and I created the subdomain briesebaer.intern. Using DNS RSAT Tool I see under briesebaer.intern the subdomain intern and then a recurrence of the whole domain. That means: under intern there is briesebaer and all of the dns query beneath. The query shows the Name=intern

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

On 09/03/18 13:30, lingpanda101 via samba wrote: > On 3/9/2018 5:30 AM, Paul Littlefield via samba wrote: >> For some reason, the provision picked up 2 network IP addresses in my VM. >> >> Snipped output below... >> >> >> root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 >>   dwVersion                   : 0xece0205 >>  

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

I noticed when Samba initially created a NS it gave it a ttl=900. If I delete this record from my zone and create a new one. It gives the NS a ttl=0. Attempting to set using Microsoft DNS tools does not take. Can this be done any other way? Using samba-tool? Thanks. Name=, Records=6, Children=0 SOA: serial=481, refresh=900, retry=600, expire=86400, minttl=0,

Hello Samba List, I have 2 problems with dns - seeing the child entries and a zone with an extra octet. First... I have created a /16 reverse zone as per the wiki page (https://wiki.samba.org/index.php/DNS_Administration#To_create_a_.2F24_reverse_zone)... $ samba-tool dns zonecreate dc3 130.130.in-addr.arpa $ samba-tool dns zonelist --reverse dc3 pszZoneName :

On 13/02/2020 13:11, Paul Littlefield wrote: > On 12/02/2020 13:08, Rowland penny via samba wrote: >> The first is that a DC must use itself as its nameserver and if >> something goes wrong e.g. Samba has fallen over, then there isn't >> much point having another nameserver, Samba isn't going to use it >> >> The second is, it will not hurt having a second