In named.conf.local I have a reverse zone
zone "30.168.192.in-addr.arpa" {
type master;
notify yes;
include "/etc/bind/xfer-policy";
file "/etc/bind/db.30.168.192";
};
Am 12.04.2017 um 12:50 schrieb Rowland Penny via samba:> On Wed, 12 Apr 2017 12:34:32 +0200
> basti via samba <samba at lists.samba.org> wrote:
>
>> Hello,
>>
>> on my Samba AD with BIND DLZ backend it looks like Reverse Updates did
>> not work.
>>
>> dig winclient.example.com resolve an IP
>> dig -x IP does not resolve the hostname
>>
>> In the bind log I see
>> client 192.168.30.148#57598: update 'example.com/IN' denied
>>
>
> Have you actually created the reverse zone ?
>
> Rowland
>
On Wed, 12 Apr 2017 13:12:42 +0200 basti via samba <samba at lists.samba.org> wrote:> In named.conf.local I have a reverse zone > > zone "30.168.192.in-addr.arpa" { > type master; > notify yes; > include "/etc/bind/xfer-policy"; > file "/etc/bind/db.30.168.192"; > }; >You should remove this and create the reverse zone in AD with samba-tool, this is where it belongs. Rowland
OK I have done and ad an reverse zone to my ad. manual added values are found now. Automatic updates (by client like ipconfig /renew) are still denied. Am 12.04.2017 um 13:28 schrieb Rowland Penny via samba:> On Wed, 12 Apr 2017 13:12:42 +0200 > basti via samba <samba at lists.samba.org> wrote: > >> In named.conf.local I have a reverse zone >> >> zone "30.168.192.in-addr.arpa" { >> type master; >> notify yes; >> include "/etc/bind/xfer-policy"; >> file "/etc/bind/db.30.168.192"; >> }; >> > > You should remove this and create the reverse zone in AD with > samba-tool, this is where it belongs. > > Rowland > >