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
Marek Kozlowski wrote:
>
> OK. Let's assume I have only one primary and only one secondary DNS. I
> have two views on my primary. May I set up the secondary one for two
> views as well I make it fully synchronized to the primary one? (AFAIK
> for `allow-transfer' I specify IP addresses -- there is
> Judicious use of views with ACLs
I haven't actually tested this, but there's a recent thread [1] which
describes what I mean. Pay particular attention to the issue of getting
master notification into the slaves.
-JP
[1] https://lists.isc.org/pipermail/bind-users/2011-May/083664.html
_
:-)
>> Or should I use separate secondary DNS servers for internal and
>> external zones?
>
> That depends a bit on your setup. Judicious use of views with ACLs
> could help you solve your problem regarding the zone transfers, but you
> may feel more comfortable with separate servers.
I understan
> May I transfer *views* rather than zone description files?
No. That's why it is called "zone" transfer. :)
> May I transfer two zone description files for a single zone to a
> single server?
Again no. (See previous thread on your request to serve two zone files
for the same zone in the one vi
:-)
I have defined two views (let's call them an `internal' and an
`external') for my zones on the primary DNS server. Let's assume I'd
like the secondary DNS server to use the same two views synchronized to
the primary DNS. May I transfer *views* rather than zone description
files? May I transfer
6 matches
Mail list logo
