amitay at gmail.com
Fri Mar 9 19:43:10 MST 2012
On Sat, Mar 10, 2012 at 9:59 AM, Andrew Bartlett <abartlet at samba.org> wrote:
> On Fri, 2012-03-09 at 16:24 -0500, Greg Dickie wrote:
>> Perhaps another stupid question but I'm trying to get bind9 DLZ to work
>> but it throws an error about
>> missing /usr/local/samba/private/dns/sam.ldb. in fact
>> the /usr/local/samba/private/dns does not even exist.
>> The DC was created with domain join and I seem to have the DNS data in
>> /usr/local/samba/private/sam.ldb.d but how to I get samba to create (and
>> update) the DNS files? I read a thread that implied they can not just be
>> copied and samba will need to keep them updated I suppose.
>> I want to transition away from the windows DC.
>> Any ideas?
> What I think we need to do is extend
> source4/scripting/bin/samba_upgradedns to cope with this situation. In
> your case, we need to create the account for BIND9 and the special dns
> directory, but we don't need to create the actual partition. This can
> be detected based on inspecting the directory.
> We should then put this into the tail of the join.py code.
> As this is your script, do you have any further thoughts?
Yes, I also thought of the same thing. Right now use samba_upgradedns
to fix the dns provision for DLZ_BIND9. I wouldn't want to add it to
join.py since it doesn't really belong there. This is just a special
solution for DLZ_BIND9. Once we have internal DNS, we don't really
need to do anything special. I will update the script, so it can be
used on provisioned database after join. In fact one should be able to
run the script without having any side effects, even if everything is
as it should be.
More information about the samba-technical