From: Jamie C. <jca...@we...> - 2001-07-21 08:37:54
|
Kenneth Porter wrote: > > Ran into another one. I've been using Webmin's bind module as just a > viewer for now, until I figure out how to add DDNS support. Meanwhile, > I removed a zone (10.in-addr.arpa) that was in the set of zones I was > allowing myself to edit, and added a couple of other zones (both > forwarders, one a forward domain and one a reverse), by editing > named.conf. When I looked at the result with webmin ("Existing DNS > Zones"), I saw the old "10" zone and not the two new ones. Clicking on > the old zone resulted in a Perl error page with the name of one of the > new zones and this message: Can't use an undefined value as a HASH > reference at /usr/libexec/webmin/bind8/edit_master.cgi line 28. It > looks like the module isn't cross-checking the information from the > webmin config files against the current state of the BIND config files. > (This was after restarting webmin, which was necessary to get your > updated bind module recognized.) That's rather odd, because if a zone no longer exists it can never appear on the zone list page, even if some user still has it in his list of allowed zones. From your description, it sounds like you had the main page of the bind module open, deleted a zone in another window and then click on the deleted zone. Can you replicate this problem in webmin 0.87 ? > When webmin is populating the list of zones one is allowed to edit, it > should remove any no longer in named.conf. If the user is only allowed > to edit selected zones, webmin should not include any new zones. > > BTW, is there some way to provide "read-only" access to a zone? I'd > like to permit some users to inspect a zone but not to change it. Yes - you can allow a user to only view zones without being able to edit them. However, this applies to all the zones the user has access to, so you can't grant edit access to some and read-only access to others. - Jamie |