Problems in views in a zone transfer

[Luis Silva]

Let me refrase my question. How can I notify a slave that suports different
views for the zone? How can the master distinguish?

Thanks in advance,
Luis

On Tue, May 10, 2011 at 2:50 PM, Luis Silva <luisfilsilva at gmail.com> wrote:

> Many thanks for the answer. Btw, If I want to notify the slaves that a zone
> is updated, which parameter (ip:port) needs to be configured in the slave to
> differenciate the view? Is the "transfer-source" also used for listening for
> the notify requests?
>
>
> On Fri, May 6, 2011 at 6:04 AM, Jeff Pang <jeffrpang at gmail.com> wrote:
>
>> 2011/5/6 Luis Silva <luisfilsilva at gmail.com>:
>> > Hi all,
>> >
>> > I'm using bind as frontend solution and I have another server as backend
>> and
>> > I'm implementing zone transfer between the two (bind is the slave and my
>> > server is the master). The problem is that I want to use dns views. Bind
>> > supports it but my backend server is currently not supporting. I'm
>> trying to
>> > find a way for distinguish the zone transfer requests for each view. I
>> have
>> > two solutions:
>> >
>>
>> Hi,
>>
>> using TSIG keys for zone transfer for multi-views, that works well.
>> My website, dnsbed.com, currently has two nameservers.
>> One is in Atlanda, another is in Fremont, CA.
>> Each nameserver has four views.
>> The zone transfer between them is run with TSIG keys, all goes well.
>>
>> --
>> Jeff Pang
>> www.DNSbed.com <http://www.dnsbed.com/>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20110510/8fde00df/attachment.html>