similar to: How to delete a corrupt record from internal DNS

On 04/01/16 17:23, Ole Traupe wrote: > No ideas on that? > > Ole > > > > Am 18.12.2015 um 13:44 schrieb Ole Traupe: >> I accidentally created a SRV record with a false port. I then updated >> the port but was afraid of any consequences. So I deleted that record >> again and wanted to re-create it. But now I can't: "The record >> already

On 08/01/16 10:31, Ole Traupe wrote: > > > Am 04.01.2016 um 19:24 schrieb Rowland penny: >> On 04/01/16 17:23, Ole Traupe wrote: >>> No ideas on that? >>> >>> Ole >>> >>> >>> >>> Am 18.12.2015 um 13:44 schrieb Ole Traupe: >>>> I accidentally created a SRV record with a false port. I then >>>>

Am 08.01.2016 um 12:03 schrieb Ole Traupe: > > > Am 08.01.2016 um 11:47 schrieb Rowland penny: >> On 08/01/16 10:31, Ole Traupe wrote: >>> >>> >>> Am 04.01.2016 um 19:24 schrieb Rowland penny: >>>> On 04/01/16 17:23, Ole Traupe wrote: >>>>> No ideas on that? >>>>> >>>>> 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 >> why log-on from member servers isn't working properly (for me). >> However, in the meantime I have created all the necessary DNS >> records. This can't be the issue anymore. >> >>

No ideas on that? Ole Am 18.12.2015 um 13:44 schrieb Ole Traupe: > I accidentally created a SRV record with a false port. I then updated > the port but was afraid of any consequences. So I deleted that record > again and wanted to re-create it. But now I can't: "The record already > exists." > > Observations: > > > 1) I can't see it in the RSAT

On 10/12/15 15:13, Ole Traupe wrote: > > > Am 10.12.2015 um 15:49 schrieb Rowland penny: >> On 10/12/15 14:40, Ole Traupe wrote: >>> >>>>> However, my 2nd DC is not that new, I restarted it many times, >>>>> just again (samba service). No DNS records are created anywhere. >>>>> >>>>> If I go through the DNS

Am 04.01.2016 um 19:24 schrieb Rowland penny: > On 04/01/16 17:23, Ole Traupe wrote: >> No ideas on that? >> >> Ole >> >> >> >> Am 18.12.2015 um 13:44 schrieb Ole Traupe: >>> I accidentally created a SRV record with a false port. I then >>> updated the port but was afraid of any consequences. So I deleted >>> that record

Am 08.01.2016 um 11:47 schrieb Rowland penny: > On 08/01/16 10:31, Ole Traupe wrote: >> >> >> Am 04.01.2016 um 19:24 schrieb Rowland penny: >>> On 04/01/16 17:23, Ole Traupe wrote: >>>> No ideas on that? >>>> >>>> Ole >>>> >>>> >>>> >>>> Am 18.12.2015 um 13:44 schrieb Ole Traupe:

On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN

Good morning :) Am 04.01.2024 um 20:17 schrieb lists--- via samba: > Am 04.01.2024 um 13:28 schrieb lists--- via samba: >> Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >>> On Thu, 4 Jan 2024 12:12:57 +0100 >>> lists--- via samba <samba at lists.samba.org> wrote: >>> >>>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba:

I installed a third DC today. Replication works find, but as systemctl status samba-ad-dc showed an error w.r.t. dnsupdate I was running samba_dnsupdate ?verbose. Below is the output. It looks like there are some missing DNS records, but what are potential causes of this error: dns_tkey_gssnegotiate: TKEY is unacceptable I already checked what?s listed @

Hi all, I posted on both mailing as this seems to be (to me) an internal issue. As the 4.3.1 went out I decided to switch my DC from 4.3.0 to this new version. The process was to install Samba 4.3.1 on new systems, joining these Samba as DC, seizing FSMO roles, demote all 4.3.0. The few I tested until now is working except for DNS entries: samba_dnsupdate is not working as it tries to update

Hello! I've followed your tutorial to change the IP Address of our Samba AD DC: https://wiki.samba.org/index.php/Changing_the_IP_Address_of_a_Samba_AD_DC But the samba_dnsupdate tool always crashes with this output: samba_dnsupdate --verbose Unknown parameter encountered: "ks" Ignoring unknown parameter "ks" IPs: ['192.168.68.201'] Looking for DNS entry A

> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

Am 04.01.2024 um 13:28 schrieb lists--- via samba: > Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >> On Thu, 4 Jan 2024 12:12:57 +0100 >> lists--- via samba <samba at lists.samba.org> wrote: >> >>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba: >>>> On Thu, 4 Jan 2024 11:19:17 +0100 >>>> lists--- via samba <samba at

Thank you for hint to this VBS script. In fact I alraedy saw it but I'm not too confident in my VB knowledge, so I didn't use that script, prefering rely on Samba command and shell scripts to work around issues. You spoke about SOA record which wasn't changed, same here. There is another DNS record I had to change: _ldap._tcp.pdc._msdcs.samba.domain.tld. I spoke about removing

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

Hi, The smb.conf is the default after the upgrade: cat /etc/samba/smb.conf # Global parameters [global] workgroup = TTU realm = ttu.red netbios name = PDC interfaces = lo, eth0 bind interfaces only = Yes server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc,

Many (many) hours later, I'm finally throwing in the towel and seeking help. I have read everything I can find on the internet to no avail to get past my issues. I have to say, I'm very disappointed in the general quality and fragmentation of information on this topic. Samba isn't a turn-key solution as an AD by any stretch of the imagination. I've run the gamut so far with