samba -b
Samba version: 4.0.0alpha18-GIT-5c53926
Build environment:
Build host: Linux hh3 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3
14:45:45 UTC 2011 (187dde0) i686 i686 i386 GNU/Linux
openSUSE 12.1 i586
Hi everyone.
After.
./source4/setup/provision --realm=hh3.site --domain=HH1
--adminpass=SOMEPASSWORD --server-role='domain controller'
The wiki howto is for DNS seems to be wrong. I had to do this:
Copy
/usr/local/samba/private/named.conf
to
/etc/named.conf.samba4
Copy
/usr/local/samba/private/dns/hh3.site.zone
to
/var/lib/named/master
edit
/etc/named.conf.samba4 to point to /var/lib/named:
one "hh3.site." IN {
type master;
file "/var/lib/named/master/hh3.site.zone";
edit /etc/named.conf to include:
include "/etc/named.conf.samba4";
as the last line in the file.
Is this correct?
On restarting bind there are still errors:
Nov 29 19:54:15 hh3 named[4038]: command channel listening on 127.0.0.1#953
Nov 29 19:54:15 hh3 named[4038]: couldn't add command channel ::1#953:
address not available
Nov 29 19:54:15 hh3 named[4038]: managed-keys-zone ./IN: loading from
master file managed-keys.bind failed: file not found
Nov 29 19:54:15 hh3 named[4038]: managed-keys-zone ./IN: loaded serial 0
DNS and Kerberos are working fine. Are these errors to do with Samba4?
Thanks
Steve.
Am 29.11.2011 19:58, schrieb steve:> samba -b > Samba version: 4.0.0alpha18-GIT-5c53926 > Build environment: > Build host: Linux hh3 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 > 14:45:45 UTC 2011 (187dde0) i686 i686 i386 GNU/Linux > > openSUSE 12.1 i586 > > Hi everyone. > After. > ./source4/setup/provision --realm=hh3.site --domain=HH1 > --adminpass=SOMEPASSWORD --server-role='domain controller' > > The wiki howto is for DNS seems to be wrong. I had to do this: > > Copy > /usr/local/samba/private/named.conf > to > /etc/named.conf.samba4 > > Copy > /usr/local/samba/private/dns/hh3.site.zone > to > /var/lib/named/master > > edit > /etc/named.conf.samba4 to point to /var/lib/named: > one "hh3.site." IN { > type master; > file "/var/lib/named/master/hh3.site.zone"; > > edit /etc/named.conf to include: > include "/etc/named.conf.samba4"; > as the last line in the file. > > Is this correct? > > On restarting bind there are still errors: > > Nov 29 19:54:15 hh3 named[4038]: command channel listening on 127.0.0.1#953 > Nov 29 19:54:15 hh3 named[4038]: couldn't add command channel ::1#953: > address not available > Nov 29 19:54:15 hh3 named[4038]: managed-keys-zone ./IN: loading from > master file managed-keys.bind failed: file not foundlooks like pure bind failure perhaps related to dnssec are youre running a chroot bind ? perhaps its looking on the wrong place for the file, try locate managed-keys.bind( if locate is installed ) to find it, or try to create it http://o-o-s.de/?p=2966 says for i.e. for debian echo "include \"/etc/bind/bind.keys\"; ">> /etc/bind/named.conf touch /var/cache/bind/managed-keys.bind but that may different with suse attention ! look other bind sites> Nov 29 19:54:15 hh3 named[4038]: managed-keys-zone ./IN: loaded serial 0 > > DNS and Kerberos are working fine. Are these errors to do with Samba4? > > Thanks > Steve. > > > > > > >-- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Am 29.11.2011 20:50, schrieb steve:> >> >> studied some faqs , this file should be autocreated >> if the related dir is writable >> restart bind ( named ) and look if the log shows the failure up again >> > > > Yep. Still there: > > Nov 29 20:49:23 hh3 named[5000]: managed-keys-zone ./IN: loading from > master file managed-keys.bind failed: file not found > Nov 29 20:49:23 hh3 named[5000]: managed-keys-zone ./IN: loaded serial 0 > Nov 29 20:49:23 hh3 named[4952]: Starting name server BIND ..done > Nov 29 20:49:23 hh3 named[5000]: running > > What is the directory that should be writeable? > Cheers > Steve.named 11828 3.2 1.5 116332 48032 ? Ssl Nov22 360:27 /usr/sbin/named -t /var/lib/named -u named sorry i have only a older suse to look at try look/cd at /var/lib/named if using chroot then try touch managed-keys-zone or in there or some subfolder ( depend on your conf ) perhaps you need chmod named:named managed-keys-zone after all , try ask on a suse list, suse people should easy answer this stuff -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria