similar to: MS DNS console for reverse zones issue

Hello, I'm resending my old message, as despite of lots of tests and checks, I still have the same problem. I'm facing a big problem with my Samba AD configuration : When trying to create a new reverse DNS zone on a DC, it fails with error : root at se4ad2:~# samba-tool dns zonecreate se4ad2 54.19.172.in-addr.arpa -Uadmin Password for [XXXXX\admin]: ERROR(runtime): uncaught exception

Hello, I'm facing a big problem with my Samba AD configuration : When trying to create a new reverse DNS zone on a DC, it fails with error : root at se4ad2:~# samba-tool dns zonecreate se4ad2 54.19.172.in-addr.arpa -Uadmin Password for [XXXXX\admin]: ERROR(runtime): uncaught exception - (1383, 'WERR_INTERNAL_DB_ERROR') ? File

Just for additionnal information, i ran during night? samba-tool domain tombstones expunge --tombstone-lifetime=0, many objects were cleaned, but nothing has change, reverse zone creation still fails. Le 03/10/2024 ? 21:09, denis bonnenfant--- via samba a ?crit?: > > Le 03/10/2024 ? 20:35, Rowland Penny via samba a ?crit?: >> On Thu, 3 Oct 2024 19:51:30 +0200 >> denis

Hi all, I've got on AD DC using Samba 4.4.3 on Centos7 which accept Kerberos connections (kinit is working), which accept ldapsearch with credentials but which refuse ldapsearch with GSSAPI. The issue does not seem to be coming from the client as I discovered this issue writing a script to test all 22 DC, and all 21 others DC are working well from that client. The error: SASL/GSSAPI

On Thu, 21 Nov 2024 15:09:49 +0100 denis bonnenfant--- via samba <samba at lists.samba.org> wrote: > Hello, I'm resending my old message, as despite of lots of tests and > checks, I still have the same problem. > > I'm facing a big problem with my Samba AD configuration : > > When trying to create a new reverse DNS zone on a DC, it fails with > error : >

hi folks, To forward everything that does not belong to AD (subdomain ad.domain.intra) to the domain "domain.intra" I configured an entry as show below in named.conf.local zone "domain.intra" IN { type forward; forward only; forwarders { 172.16.1.10; }; # ns1.domain.intra }; Within this network (172.16.1.0/24) I have dc1 (dc1.ad.domain.intra), dc2

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

> > And I would just put 'forwarders { 172.16.1.10; };' in 'options' > I already have this entry, but for reverse lookup it does not work. Eg: dig suporte.domain.intra +short 172.16.1.15 dig -x 172.16.1.15 +short shows nothing On Mon, Mar 19, 2018 at 1:59 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 19 Mar 2018 13:51:00 -0300 >

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

I suspect a zone overlap. Did you add an extra zone manualy in bind? Or something like this... You added : Zone1.Domain.TLD and then Domain.TLD But then with the reverse zones. Because this : > Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS records Does not look likes the samba_DLZ log lines but a pure bind log line. Review you bind config and

i will do so.... thanks Am 25.01.2017 um 08:46 schrieb L.P.H. van Belle via samba: > Still > > Check this line from you named config. > > include "/etc/bind/named.conf.default-zones"; > > This can cause an overlap in the zones, so be carefull with that one. > > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba

https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD helped me find that I needed to add options { [...] tkey-gssapi-keytab "/usr/local/samba/private/dns.keytab"; [...] }; That seems to have fixed my errors with DNS On Fri, May 27, 2016 at 9:26 AM, Rowland penny <rpenny at samba.org> wrote: > On 27/05/16 14:37, Jeff Sadowski wrote: >

You do what you want! The point is the clients must resolve everything. You have two options: A - client resolver is non-DC DNS server: here the non-DC DNS server must be configured to forward DNS requests about AD to AD DNS servers (to DCs) B - client resolver is AD DNS server: here AD DNS server(s) used as resolver(s) must be configured to forward any non-AD DNS request to non-DC DNS server.

Anybody knows if the Bind version on CentOS 4.4 (9.2.4) has issues with doing reverse DNS for subnets? (networks smaller than /24) I keep a reverse DNS /26 subnet on Bind 9.3.1 (Fedora) and it works fine. I've a /27 subnet on CentOS 4 (bind 9.2.4), exactly the same config just different subnets and addresses, and it does not work. I do a "dig @localhost .......in-addr.arpa. PTR"

I had left my config alone for now and dhcp still writes to DOMAIN1.SUBDOMAIN.TLD. But samba has been complaining about not being able to write to bind in its zone. [2016/05/27 07:30:06.738434, 0] ../source4/dsdb/dns/dns_update.c:295(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:295: Failed DNS update - NT_STATUS_UNSUCCESSFUL If you are right about it using kerberos I think I am

Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws

Did you try using windows RSAT tools ? On 4 Oct 2024 at 07:49 +0100, denis bonnenfant--- via samba <samba at lists.samba.org>, wrote: > Just for additionnal information, i ran during night? samba-tool domain > tombstones expunge --tombstone-lifetime=0, > > many objects were cleaned, but nothing has change, reverse zone creation > still fails. > > > Le 03/10/2024 ?

On Fri, May 27, 2016 at 10:23 AM, Rowland penny <rpenny at samba.org> wrote: > On 27/05/16 17:11, Jeff Sadowski wrote: > >> https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD >> helped me find that I needed to add >> >> options { >> [...] >> tkey-gssapi-keytab "/usr/local/samba/private/dns.keytab"; >>

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 :

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