On Mon, Jan 30, 2023 at 11:11:03AM +0100, Havard Eidnes via bind-users wrote:
> You didn't answer, though, whether the 9.16 named-checkzone will
> be able to read & correctly interpret the binary zone files 9.18
> stores in the file system, or whether there is some other and
> more preferable way
Hi,
I think you can achieve the same effect with dig, but it requires some
preparations.
First, enable zone transfers for your slave zone from 127.0.0.1: add
allow-transfer {127.0.0.1;}; to your slave zone definition (or add
127.0.0.1 there if you already have allow-transfer).
Then you can
by default, the files written by BIND when acting as a slave is
not in "text" format, but is some binary file format, I beleive
what is referred to as "raw" format.
I've avoided this, on my slaves:
zone "abundo.se" {
masterfile-format text;
};
I guess the binary format is
Hi Håvard.
I currently have 9.18.8 installed; the version of named-compilezone is the
same. As a test I just converted a text format zone file to raw and then
that raw file back to text and it looks fine to me:
- named-compilezone -f text -F raw -o junk.raw junk db.junk
- named-compilezone -f raw
> Named-checkzone and named-compilezone are the same executable.
> Named-checkzone looks up remote records to more completely
> detect configuration errors. See the man page for details.
Thanks for the hint, I apparently need to complicate my script
even more to avoid the network lookups.
You
Named-checkzone and named-compilezone are the same executable. Named-checkzone
looks up remote records to more completely detect configuration errors. See
the man page for details.
--
Mark Andrews
> On 30 Jan 2023, at 19:33, Havard Eidnes via bind-users
> wrote:
>
> Hi,
>
> by
6 matches
Mail list logo
