[Samba] Internal DNS, update of reverse zone fails

Rowland penny rpenny at samba.org
Mon Feb 17 09:24:23 UTC 2020

On 17/02/2020 08:42, kaffeesurrogat wrote:
> Dear Rowland,
> Yes, I did. I'm reading a lot. Docs, books, ... Updates of the
> dns-server via DHCP is up and running, both for the reverse lookup zone
> and the forward lookup mechanism. I've set the lease time to a very low
> value to make shure the dhcp-script has something to do and I can see
> entries changing.
> I've tested the entries with nslookup HOSTNAME and nslookup IP. This is
> working for IPse managed by dhcp. If i give a static ip to my client,
> nslookup HOSTNAMESTATIC is working. nslookup IPSTATIC does not.
> That is the thing which is a bit confusing. I'm not using BIND9, i'm
> using the internal dns of samba.
> Have fun,
> blubberbaer

Sorry, concentrated on the dhcp and missed 'static' :-(

Yes, this is how it is supposed to be, you are supposed to create the 
static dns records in AD yourself. Also, if you are using dhcp to update 
records, you need to stop your Windows trying to update their own records.


More information about the samba mailing list