similar to: SOA record in Samba Internal DNS

Forgot to reply to this Ralph Böhme <slow at samba.org> writes: > Hi Aurélien, > > On Sat, Apr 14, 2018 at 03:19:59PM +0200, Aurélien Aptel via samba wrote: >> At this point I think it should work, but I get: >> >> $ smbclient //foo.com/share -k > > I guess you need to specify the FQDN of the host, not the domain. Yes that was it, thanks! But both the

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,

Hello, I've finally decided to switch all FSMO roles from Windows 2008 R2 DC (vm-dc1) to one of the two Samba 4.12.3 DCs (vm-dc3). Here are several issues I've faced after that: 1. After connecting DNS Manager to the all DCs, I've found that the SOA record for my domain and msdcs zones still point to the former PDC - vm-dc1. Is that OK? 2. So, I've changed the SOA manually

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

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

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

On 06.06.2018 16:48, Rowland Penny via samba wrote: > It doesn't say that any more ;-) > > This is from my DCs > > root at dc4:~# cat /etc/resolv.conf > search samdom.example.com > nameserver 192.168.0.6 > root at dc4:~# hostname -i > 192.168.0.6 > > root at dc3:~# cat /etc/resolv.conf > search samdom.example.com > nameserver 192.168.0.7 > root at

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

On 31/05/18 18:44, Andrew Bartlett via samba wrote: > So there is also an easier option in the long term. Plus we will make > the online demote clean up the extra records. That would be great, because I've just cleaned up about 40 entries using the Windows DNS Manager gui tool! I also learnt a lot about adding extra NS and PTR records using this gui tool (mydomain.com and

On 6/6/2018 10:02 AM, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 15:40:48 +0200 > Ole Traupe via samba <samba at lists.samba.org> wrote: > >> >> On 06.06.2018 14:44, lingpanda101 wrote: >>>> ** SNIP ** >>>> >>>> Actually, the DCs (resolv.conf) were pointing to each other >>>> initially, and I think that was at

What do you see/get when you run: dig NS $(hostname -d) With 2 dc's you should see 2 records. In the past this was a bug at samba joins so only 1 NS record existed. Worth to have a look at. And adding this to /etc/resolv.conf: options timeout:2 options attempts:3 options rotate Also might help. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

On 13/02/2020 16:28, Paul Littlefield wrote: > On 13/02/2020 15:17, Rowland penny via samba wrote: >> The various ways have already been mentioned, but are all your DCs >> listed as nameservers (NS) in the SOA's for the forward and reverse >> zones ? > > > I think so... > > > root at dc3.mydomain.com ~ $ (screen) samba-tool dns query dc3 >

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 :

Hello List, I have successfully migrated my DCs to 4.7.6-Ubuntu However, I still have some traces of the old DCs in the DNS... $ samba-tool dns query dc3 mydomain.com @ ALL Name=, Records=8, Children=0 SOA: serial=570, refresh=900, retry=600, expire=86400, minttl=0, ns=dc3.mydomain.com. NS: samba.mydomain.com. (flags=600000f0, serial=110, ttl=900) NS: dc3.mydomain.com.

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

Hi, We have outdated SOA information in our samba DNS. We used to have a DC1, and it is no more, however it's listed in our SOA records on both remaining DC's. I think this is not correct. I am under the impression that in order to get full failover support, all DC's need to have listed themselves as SOA. This is also what google tells me:

On 12/02/2020 12:54, L.P.H. van Belle via samba wrote: > > >> Hello Louis, >> >> Thanks for your reply. >> >> For that dig command I get... >> >> >> root at dc3.mydomain.com ~ $ (screen) dig NS $(hostname -d) >> >> ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS mydomain.com >> ;; global options: +cmd

Now after a second attempt to log in under the account with redirection on Windows 8.1 I get "The Group Policy Client service failed the sign-in." "The universal unique identifyer (UUID) type is not supported." Yeah. On Tue, Nov 24, 2015 at 6:32 PM, Jeff Dickens <jeff at seamanpaper.com> wrote: > Ok, I have some results. > > On Mon, Nov 23, 2015 at 7:03 PM,

So I am still stuck. For reference here is the smb.conf on the member server: root at florence:~# more /etc/samba/smb.conf [global] netbios name = FLORENCE security = ADS workgroup = IOL realm = IOL.SEAMANPAPER.COM log file = /var/log/samba/%m.log log level = 1 dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab

I have a Samba PDC (Ubuntu 12, OpenLDAP 2.4.28, Samba 3.6.3), and at two remote sites, I have some Samba BDCs. For now I've manually entered the DCs as WINS servers on the workstations I'm using for testing. At the remote sites, I can log in with an account that has no logon path or logon home specified, and it works perfectly. But at the main site, when I try to log on to one of these