Samuel Cabrero changed bug 1186201
What Removed Added
Status NEW IN_PROGRESS
CC   conde.philippe@skynet.be, samba-maintainers@SuSE.de, scabrero@suse.com
Assignee samba-maintainers@SuSE.de scabrero@suse.com
Flags   needinfo?(conde.philippe@skynet.be)

Comment # 2 on bug 1186201 from
Hi Philippe,

> the sub zone is defined as 
> zone "samdom.pce23.net" in {
>         type master;
>         file "dyn/samdom.pce23.net";
>         also-notify { 192.168.1.120; };
>         notify yes;
>         allow-transfer  { 192.168.1.120; };
>         allow-query  { 192.168.1.0/24; 192.168.2.0/24; 192.168.3.0/24;
> 192.168.4.0/24; };
> };

the first problem is you don't have to define the zone in /etc/named.conf. You
provisioned the domain using the BIND9_DLZ backend which loads a dynamic
library to access the zone stored in /var/lib/samba/bind-dns/dns/sam.ldb.
Please remove the zone definition.

The second problem is named's systemd unit file restricts the paths named can
write to, this is the reason why you get the Read-only filesystem error. I will
open a new bug to discuss this problem with bind maintainer but meanwhile you
can add an override to workaround the problem:

# systemctl edit named.service

This will open an editor. Write:

[Service]
ReadWritePaths=/var/lib/named /run/named /var/lib/samba/bind-dns

Save the file and named should start now.


You are receiving this mail because: