On 23/11/09 18:05, Chris Buxton wrote:
> The internal-in view should have some log entry of the forwarded update. I'm
> not sure what category or severity level that would be, though.
I could not find it in either the query log or the update log. Bug?
> Of course, if you were to start using sign
On Nov 22, 2009, at 7:23 PM, Chris Hills wrote:
On 22/11/09 21:01, Chris Buxton wrote:
>> Change the zone from type forward to type slave, and add
>> allow-update-forwarding.
>>
>> zone "dyn.example.com." {
>> type slave;
>> masters { ::1; };
>> allow-update-forwarding { local-netw
On 22/11/09 21:01, Chris Buxton wrote:
Change the zone from type forward to type slave, and add
allow-update-forwarding.
zone "dyn.example.com." {
type slave;
masters { ::1; };
allow-update-forwarding { local-networks; };
};
Then in the external-in view, change allow-up
On Nov 22, 2009, at 1:49 AM, Chris Hills wrote:
> Hi
>
> I have a zone "example.com" configured in two views, internal-in and
> external-in. I have a dynamic zone "dyn.example.com" configured only as an
> external zone. Internal clients can lookup hosts in dyn.example.com, but
> cannot update (
Hi
I have a zone "example.com" configured in two views, internal-in and
external-in. I have a dynamic zone "dyn.example.com" configured only as
an external zone. Internal clients can lookup hosts in dyn.example.com,
but cannot update ("not authorised") as the updates are matched by the
zone i
5 matches
Mail list logo
