[Samba] Dynamic Updates to Bind DLZ through DHCP have repeated errors in syslog
blackbirdralph at gmail.com
Fri Jan 29 18:06:37 UTC 2021
On Fri, Jan 29, 2021 at 11:34 AM Rowland penny via samba
<samba at lists.samba.org> wrote:
> The update is failing because, for some reason, the record does not
> exist. This has nothing to do with the script, unless it is because the
> script never created it in the first place, but then surely there would
> be something in the logs about this.
> As I said, the script is run with the output of DHCP, this can succeed
> or fail, but it would be logged, at the same time, dhcp does its thing
> and this usually works. The script can fail, but dhcp work, the only
> thing that connects them is that dhcp runs the script with the required
> arguments (or not)
These records specifically are generated by the script from DHCP.
Looking at what it's passing (in the previous log file), I think the
issue is stemming from the script grabbing and passing the MAC, but
not the hostname, which is what Samba-tool uses.
I just tested it manually, and deleting a record in DNS took the following args:
samba-tool dns delete <server> <zone> <name> <Record Type> <record data>
The example I used and succeeded on manually was: samba-tool dns
delete dc1 domain.com sys-rstrebbing A 10.60.2.35 (My laptop). It ran
If I understand the logs correctly from your script, this is what it's passing:
samba-tool dns delete dc1 domain.com 0 A 10.60.2.11 <---Example based
on args given in the log file.
So would it even be possible to grab the hostname on an expiring
lease? Looking over the wiki again I noticed this comment on the code
In the on expiry block:
# cannot get a ClientMac here, apparently this only works when
actually receiving a packet
# cannot get a ClientName here, for some reason that always fails
By chance has the second one changed? Because otherwise samba doesn't
seem to allow removing the record since the name of the record
(ClientName) almost seems like it's a critical piece of this. Or if
anyone else has come to another solution to get the information
another way while the script runs.
More information about the samba