On 04/12/11 14:19, Marcel Ritter wrote:
Hi Steve,
it's quite likely, that bind running in chroot is the cause of
the problem. You can easily test it by disabling chroot for
named on SuSE systems by editing /etc/sysconfig/named
NAMED_RUN_CHROOTED="no"
If the problem is still there, try running named using strace,
and have a look at all stat()/open() calls concerning dlz_bind9.so.
This should give some hints about missing files/permissions and
may help to narrow down the problem.
Bye,
Marcel
Hi Marcel
Progress.
Removing the jail worked and named starts. It's getting better. Now I
have this:
hh3:/home/steve # host -t SRV _ldap._tcp.hh3.site.
_ldap._tcp.hh3.site has SRV record 0 100 389 hh3.hh3.site.
hh3:/home/steve # host -t SRV _kerberos._udp.hh3.site.
_kerberos._udp.hh3.site has SRV record 0 100 88 hh3.hh3.site.
hh3:/home/steve # host -t A samba.hh3.site
Host samba.hh3.site not found: 3(NXDOMAIN)
2 successes and a 1 failure.
(hh3.site is the fqdn)
The logs give this:
Dec 4 17:04:27 hh3 named[3383]: couldn't add command channel ::1#953:
address not available
Dec 4 17:04:27 hh3 named[3383]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 42
Dec 4 17:04:27 hh3 named[3383]: zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN:
loaded serial 42
Dec 4 17:04:27 hh3 named[3383]: zone localhost/IN: loaded serial 42
Dec 4 17:04:27 hh3 named[3383]: managed-keys-zone ./IN: loading from
master file managed-keys.bind failed: file not found
Dec 4 17:04:27 hh3 named[3383]: managed-keys-zone ./IN: loaded serial 0
Dec 4 17:04:27 hh3 named[3356]: Starting name server BIND ..done
Dec 4 17:04:27 hh3 named[3383]: running
Am trying hard to keep calm! I asked about the managed-keys-zone on the
openSUSE list a few days ago, but nothing.
Any ideas where to turn next?
Cheers
Steve
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
