I'd recommend checking the next four octets as well; they'll be 00 00 00 00
or 00 00 00 01.
I've hacked up a magic(5) file which seems to work for me:
$ file *
inline.aa:BIND raw format zone file v9.9
inline.aa.jnl:BIND journal file v9
Evan Hunt e...@isc.org wrote:
I'd recommend checking the next four octets as well; they'll be 00 00 00 00
or 00 00 00 01. The first of those is the format that's always been used
up to now; the second is the format that will be used in 9.9.0, starting
with the next beta.
Would it be
On Dec 1 2011, Evan Hunt wrote:
I've looked at a few of them, and I noticed that all the ones I've seen
start with the four-octet string 00 00 00 02. Is that sufficient?
I'd recommend checking the next four octets as well; they'll be 00 00 00 00
or 00 00 00 01. The first of those is the
Ho hum... does this mean that if one has been running a 9.9.0b(next) or
later and let it generate master files in the new raw format (e.g. as a
result of dynamic updates), then one would have a problem backing off to
earlier BIND versions?
Yes, but named-compilezone can convert back to the
With the pending release of BIND 9.9.0, and the beta testing my company is
currently doing, we've realized we need a good way to detect zone file type and
convert it.
Is there any simple way to look at a file and quickly determine whether or not
it's a BIND raw format zonefile, as opposed to a
I've looked at a few of them, and I noticed that all the ones I've seen
start with the four-octet string 00 00 00 02. Is that sufficient?
I'd recommend checking the next four octets as well; they'll be 00 00 00 00
or 00 00 00 01. The first of those is the format that's always been used
up to
6 matches
Mail list logo
