Enrico Scholz wrote:
>
> Unfortunately, our ISP (Deutsche Telekom) does not allow AXFR of the
> /24 zone. I solved it now by declaring an external (non-recursive)
> and internal (recursive) view, where the external one is a master
> for 2.1.10.in-addr.arpa covering only our 31-24 range. This wil
Mark Andrews writes:
> Firstly allow-query on a static stub does nothing.
ok; thx for clarifying
> You should be a master for 31-24.2.1.10.in-addr.arpa and a slave for
> 2.1.10.in-addr.arpa.
Unfortunately, our ISP (Deutsche Telekom) does not allow AXFR of the
/24 zone. I solved it now by dec
Firstly allow-query on a static stub does nothing. The parser
allows it because it has to allow every possible combination and
we missed blocking this at the post parse stage. The cache only
has one acl.
You should be a master for 31-24.2.1.10.in-addr.arpa and a slave
for 2.1.10.in-addr.arpa.
Matus UHLAR - fantomas writes:
>>I am trying to setup a nameserver which:
>>
>>a) allows recursive queries from certain clients only, but
>>
>>b) provides responses for a static-stub zone (which is used to return
>> PTR records for an RFC2317 setup)
>>
>>Although I have set 'allow-query { any;
On 28.01.15 18:39, Enrico Scholz wrote:
I am trying to setup a nameserver which:
a) allows recursive queries from certain clients only, but
b) provides responses for a static-stub zone (which is used to return
PTR records for an RFC2317 setup)
Although I have set 'allow-query { any; };' in t
Hi,
I am trying to setup a nameserver which:
a) allows recursive queries from certain clients only, but
b) provides responses for a static-stub zone (which is used to return
PTR records for an RFC2317 setup)
Although I have set 'allow-query { any; };' in the static-stub zone, I
get a REFUSE
6 matches
Mail list logo