Until a week ago I had a CentOS 6.3 system + Webmin 1.590 + Virtualmin 3.89 (not 100% sure for virtualmin).
I updated to CentOS 6.4, Webmin 1.620, Virtualmin 3.99 gpl.
The BIND8 module was working on my CentOS 6.3 64bit server and Webmin 1.590. Actually It shows me the zones, but they are all empty and I can not get the module to display them at all.
It seems a some sort of path problems. Tried various settings without luck. If I try to create a new zone it put it in /var/named instead of standard /var/named/chroot/var/named
Any hints?
Below /etc/webmin/bind8/config.
Thanks, P.
dnssectools_keydir=/var/named/dtkeys
auto_chroot=sh -c '. /etc/sysconfig/named && echo "$ROOTDIR"'
updserial_man=1
keygen=dnssec-keygen
checkconf=named-checkconf
tmpl_dnssec=0
updserial_def=0
pid_file=/var/run/named/named.pid
named_conf=/etc/named.conf
restart_cmd=restart
relative_paths=0
rev_must=0
soa_start=0
records_order=0
reversezonefilename_format=ZONE.rev
no_pid_chroot=0
short_names=0
master_dir=/var/named
master_ttl=1
chroot=/var/named/chroot
allow_comments=0
no_chroot=0
force_random=0
dnssec_period=21
updserial_on=1
named_path=/usr/sbin/named
whois_cmd=whois
dnssectools_rollmgr_pidfile=/var/run/rollmgr.pid
ndc_cmd=ndc
allow_long=0
checkzone=named-checkzone
allow_wild=1
show_list=1
rev_def=0
stop_cmd=/etc/rc.d/init.d/named stop
dnssectools_conf=/etc/dnssec-tools/dnssec-tools.conf
confirm_zone=1
forwardzonefilename_format=ZONE.hosts
by_view=0
tmpl_dnssec_dt=1
rndcconf_cmd=rndc-confgen
start_cmd=/etc/rc.d/init.d/named start
dnssectools_rollrec=/var/named/system.rollrec
rndc_conf=/etc/rndc.conf
signzone=dnssec-signzone
support_aaaa=1
ipv6_mode=1
slave_dir=/var/named/slaves
confirm_rec=0
soa_style=0
max_zones=1500
largezones=0
allow_underscore=1
rndc_cmd=rndc
other_slaves=1
As in my previous post, I experimented problems in DNS managing after webmin/virtualmin update from 1.590 to 1.620 (webmin).
Investigating the problems, I found that it was a path/names related problems.
Reading the CHANGELOG (/usr/libexec/webmin/bind8/CHANGELOG), I noticied:
---- Changes since 1.600 ---- Changed all links to zones to use the zone name instead of an index, to prevent incorrect modification during concurrent access to the module.
Replacing the whole /usr/libexec/webmin/bind8 directory (1.620) with the correspondig in the 1.590 webmin version, solve my problems.
I manage the DNS and the zone files also via some server scripts, not only via webmin/virtualmin. In fact, settings the paths in the 1.620 bind module so it can find the named.conf, I can create/manage new zones via webmin, but not the old zones that don't use the *zonefilename_format syntax. Usually I name my zones like aaaa.tld.zone o aaaa.tld.rev. If there is a way to use this instead of the ZONE.hosts/ZONE.rev default of webmin (where ZONE = DOMAIN.TLD.VIEW), and a little more flexybility in the path management, probably webmin bind module can be still used as an alternate tools to manage bind in a server, like it is in my memory from at last 15 years (I use it surely from the 0.62 version (1998), but probably from before). In the future plans for webmin/virtualmin is included the support of pre-configured system or only for webmin compliant systems?
Thanks, P.