[Samba] Samba4: Wrong computer name / IP address assignment after DHCP reset (Solved)

X-Dimension at gmx.net X-Dimension at gmx.net
Wed Oct 22 01:11:12 MDT 2014


Gesendet: Dienstag, 21. Oktober 2014 um 20:59 Uhr
Von: steve <steve at steve-ss.com>
An: samba at lists.samba.org
Betreff: Re: [Samba] Samba4: Wrong computer name / IP address assignment after DHCP reset
On 21/10/14 20:48, X-Dimension wrote:
> Am 21.10.2014 um 18:23 schrieb steve:
>> On 21/10/14 18:12, mots wrote:
>>> I've read that just now, you didn't configure your DHCP server to update
>>> DNS records if you've just followed that tutorial.
>>>
>>
>> Hi
>> bind will update windows clients with simply:
>>
>> tkey-gssapi-keytab "/path/to/samba/private/dns.keytab";
>> at /path/to/named.conf
>>
>> Make sure named has r on the keytab and rw on the dns dbs. Is the
>> problem rather with Linux boxes not updating?
>> Steve
>>
>>
> Hi Steve,
>
> i had take a look into /etc/bind/named.conf.options and
> "tkey-gssapi-keytab "/path/to/samba/private/dns.keytab"; is already set
> here.
>
> I also looked into /var/log/syslog and i have found entrys like this:
>
> client 192.168.1.82#49398: update 'mydomain.lan/IN' denied
> named[1161]: samba_dlz: cancelling transaction on zone mydomain.lan
> named[1161]: samba_dlz: starting transaction on zone mydomain.lan
> named[1161]: samba_dlz: disallowing update of
> signer=computer-2\$\@MYDOMAIN.LAN name=Computer-2.mydomain.lan type=AA$
> named[1161]: client 192.168.1.82#60064: updating zone
> 'mydomain.lan/NONE': update failed: rejected by secure update (REFUSED)
> named[1161]: samba_dlz: cancelling transaction on zone mydomain.lan
>
> It looks like only some clients have this problem and most of the other
> are doing this:

If you've only a few then quicker to to leave the domain, remove the A
using samba-tool dns and rejoin.
HTH,
Steve

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

i have removed the DNS entries of the clients that could not be updated with
the Microsoft DNS Tool. Now the clients can update DNS entries without a problem
and everything works fine again.

Thanks a lot! :)


More information about the samba mailing list