On Thu, 2022-06-09 at 07:10 -0400, Zombie Ryushu via samba wrote:> On 6/9/22 07:07, Michael Wandel via samba wrote: > > please take a look at > > > > https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records > > > > best regards > > > > Michael > > > > > Am 09.06.2022 um 13:03 schrieb Zombie Ryushu via samba < > > > samba at lists.samba.org>: > > > > > > ?I need to know if there is a way I can tell Bind with DLZ to > > > accept normal Zone updates with Bind DLZ. I would like dhcpd to > > > be able to update the zone in the manner it had before. Can Samba > > > or Bind still be told to allow updates? > > > > > > -- > > > To unsubscribe from this list go to the following URL and read > > > the > > > instructions: https://lists.samba.org/mailman/options/samba > > This is exactly what I want to avoid. The process shown on the Samba > Wiki seems failure prone. I will do it if there is no alternative, > but I > would prefer to have Zone updates done in the standard mechanism > they > have been. > >I have come to the conclusion that you will have problems with whatever you touch. I have been using versions of that script for about 8 years without major problem. I do not care whether you use it or not, it is your decision, but you are going to have to use something similar. why do you think that I went to all the trouble of writing the script in the first place ? Rowland
On 6/9/22 07:22, Rowland Penny via samba wrote:> On Thu, 2022-06-09 at 07:10 -0400, Zombie Ryushu via samba wrote: >> On 6/9/22 07:07, Michael Wandel via samba wrote: >>> please take a look at >>> >>> https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records >>> >>> best regards >>> >>> Michael >>> >>>> Am 09.06.2022 um 13:03 schrieb Zombie Ryushu via samba < >>>> samba at lists.samba.org>: >>>> >>>> ?I need to know if there is a way I can tell Bind with DLZ to >>>> accept normal Zone updates with Bind DLZ. I would like dhcpd to >>>> be able to update the zone in the manner it had before. Can Samba >>>> or Bind still be told to allow updates? >>>> >>>> -- >>>> To unsubscribe from this list go to the following URL and read >>>> the >>>> instructions: https://lists.samba.org/mailman/options/samba >> This is exactly what I want to avoid. The process shown on the Samba >> Wiki seems failure prone. I will do it if there is no alternative, >> but I >> would prefer to have Zone updates done in the standard mechanism >> they >> have been. >> >> > I have come to the conclusion that you will have problems with whatever > you touch. I have been using versions of that script for about 8 years > without major problem. I do not care whether you use it or not, it is > your decision, but you are going to have to use something similar. why > do you think that I went to all the trouble of writing the script in > the first place ? > > Rowland > > >Alright. I will do what you ask and follow proceedure. Stand by as I do so. However. While none of this is solving my original problem, it is forcing me to grow as a Samba AD Admin. (and when I am finished with this part, I do need to get back to my first problem.)
2022-06-09T09:13:33.116681-04:00 olympia dhcpd: reuse_lease: lease age 4926 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.22 2022-06-09T09:13:33.116874-04:00 olympia dhcpd: DHCPDISCOVER from 9c:2e:a1:ae:35:e9 via eth1 2022-06-09T09:13:34.118441-04:00 olympia dhcpd: DHCPOFFER on 192.168.0.22 to 9c:2e:a1:ae:35:e9 via eth1 2022-06-09T09:13:34.130323-04:00 olympia dhcpd: Commit: IP: 192.168.0.22 DHCID: 9c:2e:a1:ae:35:e9 Name: dhcp-192-168-0-22 2022-06-09T09:13:34.130545-04:00 olympia dhcpd: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh 2022-06-09T09:13:34.130640-04:00 olympia dhcpd: execute_statement argv[1] = add 2022-06-09T09:13:34.130729-04:00 olympia dhcpd: execute_statement argv[2] = 192.168.0.22 2022-06-09T09:13:34.130816-04:00 olympia dhcpd: execute_statement argv[3] = 9c:2e:a1:ae:35:e9 2022-06-09T09:13:34.130904-04:00 olympia dhcpd: execute_statement argv[4] = dhcp-192-168-0-22 2022-06-09T09:13:34.132194-04:00 olympia dhcpd: Unable to execute /usr/local/bin/dhcp-dyndns.sh: No such file or directory 2022-06-09T09:13:34.132354-04:00 olympia dhcpd: execute: /usr/local/bin/dhcp-dyndns.sh exit status 32512 2022-06-09T09:13:34.132462-04:00 olympia dhcpd: reuse_lease: lease age 4927 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.22 2022-06-09T09:13:34.132557-04:00 olympia dhcpd: DHCPREQUEST for 192.168.0.22 (192.168.0.4) from 9c:2e:a1:ae:35:e9 via eth1 2022-06-09T09:13:34.132645-04:00 olympia dhcpd: DHCPACK on 192.168.0.22 to 9c:2e:a1:ae:35:e9 via eth1 Yeah, thats what I was afraid of.