samba 4 rc1: internal dns

Michele Petrazzo michele at unipex.it
Fri Sep 14 10:30:42 MDT 2012


On 14/09/2012 18:15, Andrew Bartlett wrote:
> On Fri, 2012-09-14 at 16:57 +0200, mpe wrote:
>> On 14/09/2012 16:26, Ricky Nance wrote:
>>> For the initial join you just need to make sure that your
>>> /etc/resolved.conf is pointed at your main AD DC. After that samba can be
>>> configured with internal DNS. Look back on the list a few days for more
>>> info on it, documentation is being worked on. Remember if you are using the
>>> git version that you are using 'cutting edge' code, so documentation may
>>> not quite keep up with it :-) .
>>>
>>
>> Perfect, it works! ;)
>>
>> Next question:
>> mysrv:~#/usr/local/samba/sbin/samba -i -M single
>>
>> /usr/local/samba/sbin/samba_dnsupdate: usage: nsupdate [-d] [-y
>> keyname:secret | -k keyfile] [-v] [filename]
>> ../source4/dsdb/dns/dns_update.c:294: Failed DNS update -
>> NT_STATUS_UNSUCCESSFUL
> Your bind9-utils package (providing nsupdate) was not built with gssapi
> support (which would then give you a -g flag).

This is en error or a warning? I don't understand if samba 4 can be used 
or not.


> Having removed our dependency on bind9 as a server, we do hope to remove
> our dependency on the client as well (for this and other reasons), but
> I'm not sure if this will change for the 4.0 release.

Sorry, but:
mysrv:~# find /usr/local/samba/ -iname "*nsup*"
/usr/local/samba/sbin/samba_dnsupdate

are this the same? If yes, can we modify the sources to point to it?


> Andrew Bartlett
>

Thanks,
Michele Petrazzo




More information about the samba-technical mailing list