#2194 Delete zone tries to delete incorrect zone

[amaru]

Running Webmin 1.220 on FreeBSD 4.4 with BIND
9.3.1. I'm using Internet Explorer 6. When trying to
delete a zone it asks: Are you sure you want to delete
the 1 selected zones? (somedomain.com). The domain
is incorrect. The domain listed seems to be the last
domain I modified. If I delete it I can then go in and
delete the domain that I really want to delete. I am
having this issue on several servers.

[Jamie Cameron]

Logged In: YES
user_id=129364

I couldn't replicate this bug on my own system.
Would it be possible for you to attach your named.conf file
to this bug report, so I can see what Webmin is doing wrong?

[amaru]

Named.conf

[amaru]

Logged In: YES
user_id=1321416

I have attached one of the named.conf files.

[Jamie Cameron]

Logged In: YES
user_id=129364

I just tried that named.conf file on my system, with no
problems..
Does this problem happen every time you delete a zone, or
just occasionally?

[amaru]

Logged In: YES
user_id=1321416

Just occasionally. It's trying to delete the incorrect domain.
If I delete the wrong domain it seems to work ok after that,
but I have to go in and re-add the wrong domain that it
deleted. I just checked and it seems like every domain that I
try to delete it's trying to delete a different domain. Would
you want to login to my webmin and see what it's doing? I
appreciate your help.

[Jamie Cameron]

Logged In: YES
user_id=129364

I would be interested in seeing this myself - that would
really help me find the bug.
You can email me at jcameron@webmin.com with login
information ..

[Nobody/Anonymous]

I am also having this problem, with Webmin 1.490. It occurs no matter if I check the zone checkbox in the module index and "Delete Selected", or if I click through to the zone itself first and then click "Delete Zone". In my case, I'm trying to delete a master zone "10.1.0" I created, but it tries instead to delete zone 255.

[Jamie Cameron]

If anyone is seeing this, could you attach your named.conf file to this bug report?

[Shenan Hawkins]

My named.conf itself probably won't help much, but here it is:

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";

The real problem will be in named.conf.local, which is only:

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

zone "introverted.local" {
type slave;
masters {
10.42.0.2;
};
file "/var/cache/bind/introverted.local.hosts";
};
zone "0.42.10.in-addr.arpa" {
type slave;
masters {
10.42.0.2;
};
file "/var/cache/bind/10.42.0.rev";
};
zone "0.1.10.in-addr.arpa" {
type master;
file "/etc/bind/10.1.0.rev";
};

So now a better description about the bug that I see, if I try to delete zone "10.1.0" (?index=8), it will instead try to delete zone "255" (?index=5). 8-5 = 3, the number of custom zones I created (might be coincidence)?

[Jamie Cameron]

Which file is the zone that it incorrectly tries to delete in though?