[Samba] Reverse DNS

[Praveen Ghimire]

Hi Rowland,

I have tried putting the whole rev-domain name. The following is the dhcpd.conf zone definition

      subnet 192.168.14.0 netmask 255.255.255.0 {
        authoritative;    
        ddns-update-style standard;
        option netbios-name-servers 192.168.14.10; #14.10 is the AD box
        option netbios-dd-server 192.168.14.10;
        option netbios-node-type 8;
        option domain-name-servers 192.168.14.10;
        ddns-rev-domainname "14.168.192.in-addr.arpa.";
	 option broadcast-address 192.168.14.255;
        option routers 192.168.14.254;
        option domain-name "lin.group"; #AD DOMAIN
        ddns-domainname "lin.group";
        ddns-updates on;
        update-optimization off;
        update-static-leases on;
        allow client-updates;
pool
{
.......
}

I have removed and re-created the reverse zone a few times , selecting secure and nosecure also with and without storing the info in AD. The only time I have seen it being populated is when I assign static IPs



Regards,
Praveen Ghimire


-----Original Message-----
From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland penny via samba
Sent: Wednesday, 26 June 2019 5:06 PM
To: samba at lists.samba.org
Subject: Re: [Samba] Reverse DNS

On 26/06/2019 04:38, Praveen Ghimire via samba wrote:
> Hi Louis,
>
> Thank you for that
>
> I have made the changes as per below , some items might have 
> duplicated. I then reload apparmor restarted the samba-ad-dc and bind9 
> services and get the same issue. Every time the forward DNS update 
> works but the reverse doesn't
>
> I found a really interesting samba post going back 2017 re the DHCP 
> and DNS 
> http://samba.2283325.n4.nabble.com/DHCP-DNS-and-non-domain-members-td4
> 726681.html
>
> In the article there are suggestions of not letting Windows clients updating their own DNS records. In my test machine I manually removed the option . The error message disappears when the machine renews it's DHCP but the DNS (forward or reverse) doesn't update.
>
> The one thing I can't understand is despite the error messages in 
> syslog about denying the lin.group zone, the forward updates but the 
> reverse doesn't .  The DHCP server has the following
>
> ddns-rev-domainname "in-addr.arpa.";

But isn't your reverse zone called '14.168.192.in-addr.arpa' ?

Are your clients set to update their reverse zone ? The DHCP server will not do this by default.

Try deleting the reversezone and recreating it, it could be a permissions problem.

Rowland



--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________