similar to: Reverse dns lookup with internal DNS

Hi, I do have a domain and a couple of different ip networks. E.g. domainname.de and 172.17.0.0/16 and 192.168.200.0/24 In our old dns files I only have a reverse master zone for the 172.17.-lans, but also 192.168.200.x addresses in the forward zone config. My question: dose maybe someone forgot the 192.168.200.x reverse zone files and config and can I just create a file like that for the

Hello, I'm struggling with an error for secure dynamic dns updates for reverse lookup zones. My environment: 2 Samba 4.8.4 DC's with BIND DLZ as dns backend, running on Centos 7.5. Samba was compiled from source with default heimdal kerberos (./configure --with-systemd --enable-gnutls) /I know now that --with-systemd is not needed, but didn't now that the time of compilation/.

On Mon, Nov 11, 2019 at 05:27:03PM +0000, Rowland penny via samba wrote: > > > > Kerberos SRV _kerberos._tcp.ad.home.arpa record verified ok, sample output: > > > > Server: 192.168.183.1 > > > > Address: 192.168.183.1#53 > > > > > > > > _kerberos._tcp.ad.home.arpa service = 0 100 88 kronos.ad.home.arpa. > > > > Samba is

UNCLASSIFIED Hi, I can successfully setup an IPv6 Reverse Lookup Zone (Samba 4.8.0 Internal DNS) and add valid PTR entries using samba-tool and/or RSAT DNS. However I cannot view the PTR records with samba-tool or RSAT. [root at bilbo user]# samba-tool dns add localhost 4.e.7.c.9.3.0.b.4.7.6.0.7.8.d.f.ip6.arpa 5.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0 PTR brutus.dev.local Password for [administrator at

On Tue, Nov 12, 2019 at 07:53:06PM +0000, Rowland penny via samba wrote: > On 12/11/2019 19:24, andi via samba wrote: > > On Mon, Nov 11, 2019 at 05:27:03PM +0000, Rowland penny via samba wrote: > > > > > > > The IP above is 192.168.183.1, yet the IP for kronos (the DC) is > > > 192.168.0.5, so it will not be fine. > > Just for my understanding: The

On Sun, Nov 10, 2019 at 11:00:20AM +0000, Rowland penny via samba wrote: > On 10/11/2019 10:49, andi via samba wrote: > > Hello, > > > > I have configured an samba AD DC for use with > > some windows and linux machines. The linux machines use > > samba for user auth and also as kerberos kdc for > > nfs mounts. This works fine so far but after a while >

On 11/11/2019 16:47, andi wrote: > On Sun, Nov 10, 2019 at 07:19:40PM +0000, Rowland penny via samba wrote: >> On 10/11/2019 17:49, andi via samba wrote: >>> Maybe one thing in advance: I'm using a typical DSL wallbox which is doing >>> telephone, dhcp and dns (.183.1 address) I have setup its internal DNS so that >>> ad.home.arpa, .ad.home.arpa and

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 :

How is the reversed domain handled, or is it not. Rowland, you did not have that in your sample you cobbled together. In /usr/share/samba/setup/named.conf there is: zone "123.168.192.in-addr.arpa" in { type master; file "123.168.192.in-addr.arpa.zone"; update-policy { grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. PTR;

On Sat, 21 Jul 2018 20:57:07 +0200 Kacper Wirski via samba <samba at lists.samba.org> wrote: > Hello, > > I found this bugged record with > > ldbsearch -H > path/to/samba/bind-dns/dns/sam.ldb.d/DC\=DOMAINDNSZONES\,DC\=SUBDOMAIN\,DC\=DOMAIN\,DC\=PL.ldb > '(name=49)' > > So I have a couple of questions - hopefully someone can shed some > light: >

Last month I struggled with a severe DLZ issue and today I could solve it. Credits for the important idea go to Peter Serbe, thanks! I checked the DNS contents using RSAT. There was nothing wrong with SOA nor NS entries, but the reverse zones were actually forward zones with proper names in the in-addr.arpa. domain. I built proper reverse zones and deleted the forward-reverse zones and Bind

Hi everyone. I have a Linux nsupdate client sending dns update requests via sssd. Just gone from 4.1.2 to 4.1.3. I've done this: http://linuxcostablanca.blogspot.com.es/2013/09/samba4-bind9dlz-stale-dns-records-with.html After which the forward zone update is working fine: 2014-01-10T12:32:35.376142+01:00 hh16 named[4963]: samba_dlz: starting transaction on zone hh3.site

And some more information about this strange effect apparently no-one has seen before. I now added the missing zone: samba-tool dns zonecreate verdandi 10.16.172.in-addr.arpa -U Administrator and it claims that the zone is okay, but the next one is missing: Dec 29 10:31:12 verdandi named[2601]: Loading 'ad.microsult.de' using driver dlopen Dec 29 10:31:12 verdandi named[2601]:

On Tue, 6 Nov 2018 11:24:43 +0100 Kacper Wirski via samba <samba at lists.samba.org> wrote: > Hello, > > I'm struggling with an error for secure dynamic dns updates for > reverse lookup zones. > > My environment: > > 2 Samba 4.8.4 DC's with BIND DLZ as dns backend, running on Centos > 7.5. Samba was compiled from source with default heimdal kerberos

Hi, I may well be missing something obvious, or quite possibly I am wrongly thinking that things should work in a certain way - so I thought I would ask here first :) I am running a Samba 4.7.7 AD domain consisting of 4 DCs using Samba's internal DNS, and I am using Windows' 'DNS Manager' MMC tool as admin. Under "Forward Lookup Zones" I have "mydomain.org",

On 2016-10-08 07:58, Rowland Penny via samba wrote: > On Sat, 08 Oct 2016 07:50:03 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have built a second dtdc03 and joined to my first dtdc01. Thought >> all was well but, discovered that reverse dns is not correct on second >> dtdc03. >> >> root at dtdc03:~# host dtdc03

I have built a second dtdc03 and joined to my first dtdc01. Thought all was well but, discovered that reverse dns is not correct on second dtdc03. root at dtdc03:~# host dtdc03 dtdc03.dtshrm.dt has address 192.168.16.49 root at dtdc03:~# host 192.168.16.49 Host 49.16.168.192.in-addr.arpa. not found: 3(NXDOMAIN) root at dtdc03:~# nslookup dtdc03 Server: 192.168.16.49 Address: 192.168.16.49#53

On 09/03/2015 04:55 PM, Rowland Penny wrote: > On 03/09/15 21:38, Robert Moskowitz wrote: >> How is the reversed domain handled, or is it not. Rowland, you did >> not have that in your sample you cobbled together. >> >> In /usr/share/samba/setup/named.conf there is: >> >> zone "123.168.192.in-addr.arpa" in { >> type master; >>

Hi Guys, I've two DC (Zentyal Samba 4.7.6) and put new DC (Centos 7, Samba 4.7.6) with additional domain controller and works fine. My question is about reverse zone. The original DC (zentyal1 and zentyal2) have a reverse registres ``` root at zentyal1:/etc/bind# dig +noall +answer -x 10.13.250.110 110.250.13.10.in-addr.arpa. 259200 IN PTR zentyal1.example.com. root at zentyal1:/etc/bind# dig

Hello, I have configured an samba AD DC for use with some windows and linux machines. The linux machines use samba for user auth and also as kerberos kdc for nfs mounts. This works fine so far but after a while the user can not access the nfs shares anymore. I tried to analyze the problem and finally found, that the obtaining a ticket for nfs service failes in this case because of a wrong