similar to: PTR records not being created / updated

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian Naumer via samba > Verzonden: donderdag 27 februari 2020 10:33 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] New PTR records not visible > > Hello Louis, > thanks for looking into this. Have you looked at what the original > poster shared in the

Hello Lois, thanks for looking into this. Have you looked at what the original poster shared in the bug report? https://bugzilla.samba.org/show_bug.cgi?id=14268 I don't have a big problem with this, just trying to help. Maybe the original poster can say more with regards of the problem he has with this. here are more of my details. Regards #####samba-debug-info.txt##############

Yet that still does not explain why the PTR record I create for that IP does not become visible. I can create other PTR records in the same zone and they do become visible to DNS lookups. I suspect it has something to do with half-dead entries in the database that are blocking it... Thanks for looking into this, Christian On 27/02/2020 11:31, L.P.H. van Belle via samba wrote: > Ok, we might

@Heinz, Thanks for testing also, but what is your samba version, OS and packages samba of compiled samba. To keep info bit more complete @Christian, can you try purge the deleted DNS records. Can you also add the debug 10 log, shown below to this bugreport. https://bugzilla.samba.org/show_bug.cgi?id=14268 I'll retest it here later on today with a few more zones. But i must finish some

Cheers Rowland, There is a GPO in place to do that. But it?s not working. I have my notes here: http://samba.bigbird.es/doku.php?id=samba:update-dns Also, I can?t create / update PTR records using DNS tool??from RSAT then creating / updating the A record, despite selecting the option. Thanks, On Jan 17, 2024 at 10:25 +0100, samba at lists.samba.org <samba at lists.samba.org>, wrote: >

Ok, we might have found something here. I created a small script, see below, easy to adapt. So, after running this i see the same problem as in : https://bugzilla.samba.org/show_bug.cgi?id=14268 If i do it manualy everything works fine. But if i "past the commands or run the script" Then i see this problem.. So im thinking here, the speed of adding is creating somekind or

Ok, new test. Besides that i dont like the python errors shown, this still looks good. So i dont know.. See below, i can not make it error. for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do samba-tool dns add dc1.internal.dom.tld $x.249.10.in-addr.arpa 158 PTR host-test.extrazone.dom.tld ; done Record added successfully Record added successfully Record added successfully Record added

So strange.. I copied your commando's only change the arpa and servername / domainnames All worked. So far nobody told how there ad-dc and DNS is setup.. Which i why i added : > > Debian 10, my own packages. > > Samba 4.11.6 + BIND9_DLZ is used . Now are you using samba DNS or BIND_DLZ dns ? That might help here. Greetz, Louis > -----Oorspronkelijk

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 [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via > samba > Verzonden: woensdag 25 januari 2017 1:26 > Aan: samba at

I have restored the container from an early snapshot. This has all bits installed, but no config and not joined. I needed -U with a username. By the way my network is a /22 root at member:~# samba-tool dns zonelist awing.mad.mater.int --reverse -U?MAD\luis" WARNING: Using passwords on command line is insecure. Installing the setproctitle python module will hide these from shortly after

Hai Christian, > Can someone reproduce this? No, tried, but sorry, works fine for me on my 4.11.6 server. And what is you try it like this. samba-tool dns add dc1.zone1.domain.de 0.168.192.in-addr.arpa 157 PTR zone1.domain.de -U Administrator samba-tool dns add dc1.zone1.domain.de 1.168.192.in-addr.arpa 157 PTR zone2.domain.de -U Administrator I tested on my production where i have 6

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

On Wed, 17 Jan 2024 09:58:06 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > Tobias, > > Appreciate your insight, it is just nice to have, but I hate when > things don?t go as expected. I?m going to fight this a little, just > to see If I am doing anything wrong - but not that it?s critical to me > > Thanks, > On Jan 17, 2024 at 09:48 +0100,

On Sat Jan 20 16:28:14 2024 Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sat, 20 Jan 2024 15:44:18 -0500 > Mark Foley via samba <samba at lists.samba.org> wrote: > > > After provisioning and testing my new DC offline, I now want to move > > it into production. This means changing IPs. > > > > DC FQDN: mail.hprs.local > >

Tobias, Appreciate your insight, it is just nice to have, but I hate when things don?t go as expected. I?m going to fight this a little, just to see If I am doing anything wrong - but not that it?s critical to me Thanks, On Jan 17, 2024 at 09:48 +0100, Pluess, Tobias <tpluess at ieee.org>, wrote: > > Hi Luis > > I noticed exactly the same behaviour. > I wonder if the PTR

On Sat, 20 Jan 2024 20:31:31 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > On Sat Jan 20 16:28:14 2024 Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Sat, 20 Jan 2024 15:44:18 -0500 > > Mark Foley via samba <samba at lists.samba.org> wrote: > > > > > After provisioning and testing my new DC offline,

On Sat, 20 Jan 2024 15:44:18 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > After provisioning and testing my new DC offline, I now want to move > it into production. This means changing IPs. > > DC FQDN: mail.hprs.local > > IPs for setup/testing: > > DC: 192.168.1.60 > Gateway: 192.168.1.1 (Netgear router) > DNS: 192.168.1.60

On 02/08/2023 17:14, Chris Nighswonger via samba wrote: > Hello all, > > After several days of working on this, I'm stuck. Hopefully someone can point out what I'm missing here. > > I'm working with this script to dynamically update my Samba AD DC DNS: > > https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records > > Short of it: > >

After provisioning and testing my new DC offline, I now want to move it into production. This means changing IPs. DC FQDN: mail.hprs.local IPs for setup/testing: DC: 192.168.1.60 Gateway: 192.168.1.1 (Netgear router) DNS: 192.168.1.60 (/etc/resolv.conf) /etc/hosts: 192.168.1.60 mail.hprs.local mail smb.conf, dns forwarder: 192.168.1.1 Production IPs: DC: 192.168.0.2 Gateway:

On Fri, 04 Nov 2016 11:49:16 -0500 Bob of Donelson Trophy <bob at donelsontrophy.net> wrote: > On 2016-11-04 11:31, Rowland Penny via samba wrote: > > > <<<<< cut >>>>>>>> > > > >> root at dtdc03:~# samba-tool dns zonelist dtdc03 > >> 3 zone(s) found > >> > >> pszZoneName :