add record: www2; 10.2.3.1; update reverse = Yes 4.
add record: www3; 10.2.3.3; update reverse = Yes 5.
My DHCP server can update the forward zone, but not the reverse.
I found some references to issues with App Armour so I turned it off, but I still have the issue.
The way I accomplish this is with reverse DNS, correct? [email protected] /etc/bind/zones $ This isn't a problem with your reverse lookup zone, it's a problem with your forward lookup zone.
basically, you need to create an RNDC key and a assign that RNDC key updateable access from your pc.
I've noticed that webmin isn't creating reverse PTR records when adding an A record to a DNS zone if another PTR with the same address already exists.
Picking the "Yes, and replace existing" option when creating the A record will work.
You will already find general information on the internal DNS and the BIND DLZ module and documentation about Bind as DNS Backend in the Wiki.
By default, Samba creates the following two forward zones during provisioning/upgrading (of course with your own domain name): The Samba internal DNS is a new implementation.