similar to: wbinfo --dc-info finding only one of my dc's

hmm.. wbinfo --dc-info=DOMAIN for me also 1 DC its the dc its authenticated with. And what does host samba.company.com tell you? ( my out put. ) host internal.domain.tld internal.domain.tld has address 192.168.1.2 internal.domain.tld has address 192.168.1.1 internal.domain.tld mail is handled by 10 smtp.internal.domain.tld. greetz, Louis > -----Oorspronkelijk bericht----- >

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:

On 15/09/2019 19:08, Bart?omiej Solarz-Nies?uchowski wrote: > W dniu 2019-09-15 o?18:32, Rowland penny via samba pisze: >> On 15/09/2019 16:44, Bart?omiej Solarz-Nies?uchowski wrote: >>> I have some questions: >>> >>> I not currently understood - bind9 connected to AD server must be >>> used by the LAN workstations - or only via AD server? >>>

Hi, Samba: 4.12.0 During the migration from Windows DCs to Samba DCs, the following issue came up: after transferring PDC emulator role to a samba DC, the according DNS record wasn't re-created: # samba-tool fsmo show -d 0 | grep PdcEmulationMasterRole PdcEmulationMasterRole owner: CN=NTDS

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

We already "solved" this by using the long form of the domain name, but I want to learn if we should do something additional: We had a mixed setup in the field, some PCs had a WINS server configured, some not. We removed the WINS info from DHCP and saw no new problems (we wanted to have things the same way on all clients). Yesterday the local admin tried to join a new PC and entered

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 DNS gui, so I can't delete it there. 2) I also can't delete it via samba-tool (although I could delete

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

On 11/19/2015 9:44 AM, Thierry Hotelier wrote: > hello, > we've just upgraded from samba 3.6.6 to samba 4.3.0. We are using > INTERNAL as dns backend. We have 1 domain and 6 DCs on 5 different > sites. Replication between DCs is ok as we can see with "samba-tool > drs showrepl". We configured them like it is described on the wiki and > used the RSAT tool

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

Hello, sorry to ask this many questions, but I want to know why things happen they way they do and if perhaps something is wrong. Our new, shiny domain created by classicupgrade consists of 4 (four) domain controllers. dc1 was the first, which was created by classicupgrade. Then I added dc2, dchks and dcirm using samba-tool domain join iww.lan DC -U "IWW\Administrator"

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

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

Hai,   Im wondering, im missing the  _ldaps._tcp. INTERNAL.DOMAIN.TLD entries in my dns. Now, before the updates ( badlock ) etc. this wasnt notice i think. But now since im setting up that everything is doing ldaps i noticed this in my squid setup   ( squid mailing subject : [squid-users] ext_kerberos_ldap_group_acl problem )   My question is...   did someone resently setup a new AD

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

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 @

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

> 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

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