similar to: DNS /16 reverse zone issues with children and octets

Hi Paully I can help with showing the "subgroup" 0: instead of @ use 0 samba-tool dns query dc3 130.130.in-addr.arpa 0 ALL the additional 0 might be a bug in 4.7, which is end of life; I would suggest to upgrade first......but Rowland will know more about it probably. br Mani On 03.11.2020 11:24, Paul Littlefield via samba wrote: > Hello Samba List, > > I have 2 problems

On 03/11/2020 11:49, Rowland penny via samba wrote: > That is strange, first thought is that it is possibly a Windows bug, if anything Windows should refuse to show any IPv4 address with more than 4 octets. Have you tried checking the records in AD with ldbsearch ? I haven't tried that 'ldbsearch' yet - can you give me an example please? Forward and reverse DNS lookups work... $

On 03/11/2020 10:24, Paul Littlefield via samba wrote: > > $ samba-tool dns query dc3 130.130.in-addr.arpa @ ALL > > ? Name=, Records=3, Children=0 > ??? SOA: serial=32, refresh=900, retry=600, expire=86400, minttl=3600, > ns=dc3.mydomain.com., email=hostmaster.mydomain.com. (flags=600000f0, > serial=32, ttl=3600) > ??? NS: dc3.mydomain.com. (flags=600000f0, serial=1,

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

Guys, what i noticed. Look at this. Refused- 1/3/0 (Class 254) ( /24 ) Paully used /16 update 1/3/1 (Class 254) CNAME V-RDS02.mydomain.com CNAME ? And, if he uses in his example samba-tool dns add dc3 mydomain.com V-RDS02 A 130.130.0.252 A record was used. Is resolv.conf checked and it is sure in pointing to the correct DNS of the AD first? addresses: -

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

On 03/02/2020 18:49, Kris Lou via samba wrote: > > From windows: > echo %logonserver% \\DC3 > nltest /dsgetdc:<domain> DC:\\DC3 Address: \\192.168.0.218 Dom Guid: bla bla bla ... The command completed successfully. > From a *nix domain member (i.e. client, not DC): > wbinfo --getdcname=<domain> > winbind --ping-dc wbinfo --getdcname=MYDOMAIN DC3 wbinfo

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 Thu, 31 May 2018 09:42:50 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote: > On 29/05/18 12:55, Paul Littlefield via samba wrote: > > 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

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

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

Sorry Paully, I thought i already replied it. The configs look good. Did a look back in time.. And Ahh.. Now this i missed. * yesterday, we changed the IP addresses of our DCs and the Wiki page did not mention (IMHO) 2 critical things... ... So you even missed more. Review all DNS entries for the problem DC and review your AD again. rgrep /etc and /var for all the old ip numbers and/or

Hello Kris, On 03/02/2020 07:15, Kris Lou via samba wrote: > Unless it's_not_ a global catalog. Check your SRV records again, there > should be corresponding "_gc" records (similar to "_ldap") for each DC. Checked and both DCs pass all tests:- host -t SRV _ldap._tcp.mydomain.com. host -t SRV _gc._tcp.mydomain.com. host -t SRV _kerberos._udp.mydomain.com. host -t

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,

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

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 02/03/2020 11:51, Paul Littlefield via samba wrote: > On 02/03/2020 10:49, Rowland penny via samba wrote: >> Does your DC have a fixed IP and if not, why not ? > > Yes, using netplan in Ubuntu 18.04... > > network: > ? ethernets: > ??? ens18: > ????? addresses: > ????? - 130.130.0.218/16 > ????? gateway4: 130.130.0.1 > ????? nameservers: > ???????