Bug 232412

Can you please attach y2logs. If you are in doubt please follow:
http://en.opensuse.org/Bugs/YaST.


Thanks!

Created attachment 112254 [details]
The YaST2 Log

In a slave zone the allow-transfer was written ?

Could you, please, write more information how to duplicate the error?

My work-flow was:
1.) Start YaST DNS-Server
2.) Add new "master" zone with name "new.zone"
3.) Edit "new.zone"
    Leave [x] Enable Zone Transport check-box selected
    Leave [x] any ACL selected
4.) Save all settings

5.) Check /etc/named.conf
--- cut ---
zone "new.zone" in {
        allow-transfer { any; };
        file "master/new.zone";
        type master;
};
--- cut ---

6.) New zone "new.zone2"
7.) [ ] Enable Zone Transport (not selected)
8.) Check /etc/named.conf
--- cut ---
zone "new.zone2" in {
        allow-transfer { none; };
        file "master/new.zone2";
        type master;
};
--- cut ---

9.) "new.zone3"
10.) [x] Enable Zone Transport
    [x] localhost
    [x] localnets
11.) Check /etc/named.conf
--- cut ---
zone "new.zone3" in {
        allow-transfer { localhost; localnets; };
        file "master/new.zone3";
        type master;
};
--- cut ---

It works for me... where is the problem that I can't see?

Ok ;)

I create a master zone and a reverse zone like example.prv and 112.168.192.in-addr.arpa with allow-tranfer localnets and activate ldap, after save I have no allow-transfer.

Next,
1.) Start YaST2 DNS-Server in graphic mode
2.) Edit "example.prv"
    Leave [x] Enable Zone Transport check-box selected
    Leave [x] any localnets selected
4.) Save all settings

--- cut ---
zone "example.prv" in {
	file "master/example.prv";
	type master;
};
zone "112.168.192.in-addr.arpa" in {
        file "master/112.168.192.in-addr.arpa";
	type master;
};

--- cut ---

Is this a Problem with a reverse zone ?

Hmm, this produced:
--- tuck ---
zone "112.168.192.in-addr.arpa" in {
        allow-transfer { any; };
        file "master/112.168.192.in-addr.arpa";
        type master;
};
--- tuck ---
for me...

Which version of yast2-dns-server do you have installed
(`rpm -q yast2-dns-server`)? I have yast2-dns-server-2.14.2-10

What happens if you select another ACL?

By the way, when allow-transfer is not present, it actually means the very same as 

allow-transfer { any; };

because that's the BIND's default.
Disabling the transfer must be done this way:

allow-transfer { none; };

#6
I have also yast2-dns-server-2.14.2-10

I have this Problem also with SLES10, I can't configure allow-transfer ?

#7

I configure a acl Test, and enable test only and test + localnets in my named.conf i have no allow-transfer :(.

I delte all zone file and create a new one no allow-transfer.

I write in the named.conf

zone "example.prv" in {
        allow-transfer { localhost; localnets; };
        file "master/example.prv";
        type master;
};
zone "112.168.192.in-addr.arpa" in {
        file "master/112.168.192.in-addr.arpa";
        type master;
};

after start yast2 named-server the allow-transver is on any !!

When I save all chanches I have NO allow-tranfer ?

Ad #6: SLES10 had a problem with allow-transfer option (when disabling transfer), nevertheless, both SLE 10 SP1 and openSUSE 10.2 have it fixed already.

I can't reproduce the error anywhere...

Have you reproduced it on another 10.2 installation?

I installed SLES10 SP1 Beta2, with the same result ?

It's also not possible to write it manuali in the named.conf, it was deleted afetr start yast2 DNS Server Module.

When I create a slave Zone, it is written correct ?

Created attachment 115816 [details]
The YaST2 created named.conf

Created attachment 115817 [details]
YaST2 log SP1

That's very strange. Could you, please try to disable AppArmor when running these tests?

I make a rcapparmore stop, twize ;).
rcapparmor status (not running)

Then with YaSt2 DNS Server a change in the allow-transfer

same Result ?

no change, in the slave zone it was written in the master zone no :(.

Just my last idea...

Maybe it is because LDAP is used for storing zones, but I think that the /etc/named.conf should be the same even if you use LDAP server...

Hmm, I've tried also Use LDAP / Do Not Use LDAP but with the same result, everything works fine (SLE10 SP1 Beta2, comment #11).

Reassigning to QA to try to reproduce the error. I'm just unable to reproduce it, without being able to do it, I can't fix anything.

Today I am testing it again (SP1) with the ncurses Version of Yast, in the first part of the test i have the same problem (no allow-transfer). then I create a ACL and start yast again and now ,it is written (the first time) ???????

Then after next start of YaST, it was deleted again, and now I can't reproduce it  ?? (written allow-transfer).

What I can't understand, when I write it by hand, in the named.conf it was deleted from Yast in the master Zone, in the slave zone I can do it by hand or YaST ??

I send the Yast2 Log.

Can you have I look on the parser for the named.conf. I have normal a destroyed ACL (Problems // # and Tabs)

Created attachment 117358 [details]
The last YaST2 Log's (SP1)

Hi,

#16

my last idea ;)

some times the correct zone file is created from YaST2, but only on this Place in the named.conf

# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";
logging {
	category default { log_syslog; };
	channel log_syslog { syslog; };
};
zone "gjn.prv" in {
	allow-transfer { localhost; localnets; };
	masters { 192.168.100.201; };
	file "slave/gjn.prv";
	type slave;
};
zone "4gjn.prv" in {
	allow-transfer { localhost; localnets; };
	file "master/4gjn.prv";
	type master;
};
zone "112.168.192.in-addr.arpa" in {
	allow-transfer { localhost; localnets; };
	file "master/112.168.192.in-addr.arpa";
	type master;
};

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.

...

when YaST2 the zone creates on this place in the named.conf, it is always without allow-transfer ?


# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";
logging {
	category default { log_syslog; };
	channel log_syslog { syslog; };
};
zone "gjn.prv" in {
	allow-transfer { localhost; localnets; };
	masters { 192.168.100.201; };
	file "slave/gjn.prv";
	type slave;
};

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
zone "4gjn.prv" in {
	file "master/4gjn.prv";
	type master;
};
zone "112.168.192.in-addr.arpa" in {
	file "master/112.168.192.in-addr.arpa";
	type master;
};

Seems this is fixed now.