I think I can see the cause of this problem - Webmin is configured to
add new BIND zones to /etc/named.conf.local , but there is no directive
in /etc/named.conf to include this file. The quick fix is to click on
the Module Config link, and change the 'Add new zones to file' option to
'Default'.
- Jamie
On Wed, 2006-02-01 at 00:57, Rodney Richison wrote:
> It's not like I don't muck around with this every day at work, but here,
> on my home network, I'm having trouble with the bind module.
>
> I'm sure it's something simple. I've a local server behind my firewall.
> Bind works as expected. However, when I try to create a master, it
> creates it, then shows the page to change the records, yet when I click
> on something like a or nameserver record. I get a page that is pretty
> much blank, with no input boxes and the word "in" in the middle of the
> page.
>
> The strange thing is, I reproduce the error on my local machine. Both
> machines running debian. Both machines upgraded to the latest greatest
> webmin and bind modules. That's why I'm sure I'm missing something
> simple. Ideas?
>
> BTW, I can then cancel out, and no master zone has been created
> "according to webmin". However, if I then try to create it again, I get
> the message "already exists". Looking at /etc/bind, I see it does exist
> in named.conf.local and the zone file exists. So it's though webmin
> creates it, yet cannot edit it?? Or see it???
>
> Bind is on debian stable.
> Things I've tried, purge bind, remove webmin module, upgrade webmin...
> I'm out of ideas at the moment.
>
> ?????
|
