samba - Dec 2011 - DNS update failed! - Samba 3 joining Samba 4 AD Domain

Hi All,

I've got samba4 set up as AD domain controller (from latest git), works 
fine. I'm now attemptng to use a separate samba 3 box as the file server 
(as I'm assuming this is current best practice?) but when joining the 
domain (which succeeds) I get the message 'DNS update failed!'. I've
seen a lot of issues with this whilst trawling the net but no solutions.

Windows clients can join the domain, it's only samba3 clients that 
can't. I haven't done anything special on the S3 clients (as I
didn't
need to with the windows clients) but maybe I need to?

Anyway, if anybody has any ideas I'd be grateful.

Mike
-- 

*//*
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: disclaimer.txt
URL:
<http://lists.samba.org/pipermail/samba/attachments/20111216/f25c8452/attachment.txt>

Hi All,

I've got samba4 set up as AD domain controller (from latest git), works 
fine. I'm now attempting to use a separate samba3 box as the file server 
(as I'm assuming this is current best practice?) but when joining the 
domain (which succeeds) I get the message 'DNS update failed!'. I've
seen a lot of issues with this whilst trawling the net but no solutions.

Windows clients can join the domain and have DNS updated, it's only 
samba3 clients that can't. I haven't done anything special on the S3 
clients (as I didn't need to with the windows clients) but maybe I need to?

Anyway, if anybody has any ideas I'd be grateful.

Mike.

-- 
Michael Howard        mike at dewberryfields dot co dot uk
Lancashire
England

Hi

On 16 December 2011 15:34, Mike Howard <mike.howard at uretek.co.uk>
wrote:
> Hi All,
>
> I've got samba4 set up as AD domain controller (from latest git), works
> fine. I'm now attemptng to use a separate samba 3 box as the file
server (as
> I'm assuming this is current best practice?) but when joining the
domain
> (which succeeds) I get the message 'DNS update failed!'. I've
seen a lot of
> issues with this whilst trawling the net but no solutions.
>
> Windows clients can join the domain, it's only samba3 clients that
can't. I
> haven't done anything special on the S3 clients (as I didn't need
to with
> the windows clients) but maybe I need to?
>
> Anyway, if anybody has any ideas I'd be grateful.
Search the samba-technical list archives.  There have been various
messages about Samba 4 DNS and problems with dynamic DNS updates from
Samba 3.

Also, try running bind, Samba 4 and Samba 3 with the debugging turned
up and see what the actual error is.  Maybe something to do with
Kerberos?

I haven't tried joining Samba 3 to Samba 4, so not sure I can help
more than that.

-- 
Michael Wood <esiotrot at gmail.com>