Notifies are also a challenge. The two solutions are:
-Use TSIG for the notifies and zone transfers.
-Use extra IPs: on each primary and secondary, set up an IP
address dedicated to notifies and transfers for a specific view.
Your first view can use your preexisting IP but each additional
view al
> 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 th
On Nov 30, 2011, at 4:39 PM, Mark Elkins wrote:
All this comes about as I had the expectation that DIG would run in a
similar way to any other 'dns lookup' - which it currently doesn't.
It is what it is, but I've always considered dig to be a tool
aimed at giving you a means of doing lookups in
Evan wrote on 12/01/2011 05:44:02 PM:
> > 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 f
nsdiff is an add-on tool for BIND that compares old and new versions of a
zone and generates an nsupdate script that turns the old version into the
new version. It is designed to bridge the gap between static master files
and dynamic DNS updates, making it easier to use "auto-dnssec maintain".
htt
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 th
Evan Hunt 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 possible fo
> 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
8 matches
Mail list logo