rndc addzone, global allow-new-zones, 'file not found'

[Tobias Wolter]

On Wed, 11 Dec 2013 10:54:30 +0000
Tony Finch <dot at dotat.at> wrote:

> Tobias Wolter <tobias.wolter at b1-systems.de> wrote:
> >
> > # rndc -s localhost -c ~/rndc-localhost.conf addzone metazone. '{type master; file "master/metazone.zone";};'; tail /var/log/messages -n 4
> > rndc: 'addzone' failed: file not found
> > Dec 11 10:01:15 <hostname> named[21120]: received control channel command 'addzone metazone. {type master; file "master/metazone.zone";};'
> > Dec 11 10:01:15 <hostname> named[21120]: zone metazone/IN: loading from master file master/metazone.zone failed: file not found
> > Dec 11 10:01:15 <hostname> named[21120]: zone metazone/IN: not loaded due to errors.
> > Dec 11 10:01:15 <hostname> named[21120]: addzone failed; reverting.
> 
> You need to create the master file (with valid zone contents) before
> running rndc addzone.

Thank you. I know this approach works, but I was under the impression
it also works by dynamically making a zone available without needing to
create a zone file.

It's a bit of a luxury problem, I know, but that'd actually be rather
helpful in my zone replication use case here...

-towo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20131211/2b18a184/attachment.bin>