OK,
now got the soultion. I moved the statement blackhole within in the options
{} and now is accepted.
I was trying to use it in zones, which is not recognized.
Sorry for the noise.
On Fri, Dec 7, 2012 at 1:50 AM, Paolo Aglialoro <paol...@gmail.com> wrote:
> Well,
>
> thanks for answer, but I still get the same problem. I tried to put
> blackhole out of zone statement in the general area, but the error is still
> the same:
>
> # grep blackhole named.conf
> blackhole { spooferz; };
> # named-checkconf ./named.conf
> ./named.conf:18: unknown option 'blackhole'
>
> I'm getting rather crazy.... might there be any difference about sparc64
> arch?
> Could you please post your named.conf for reference?
>
>
>
> On Fri, Dec 7, 2012 at 1:07 AM, Philip Guenther <guent...@gmail.com>wrote:
>
>> On Thu, Dec 6, 2012 at 3:47 PM, Paolo Aglialoro <paol...@gmail.com>
>> wrote:
>> > This is 5.2 on sparc64.
>> > Both in BIND9 admin guide and in man named.conf the option "blackhole"
>> is
>> > present.
>> > Nevertheless, this is the story:
>> >
>> > # named-checkconf -t /var/named/
>> > /etc/named.conf:111: unknown option 'blackhole'
>> ...
>> > Is it missing in OpenBSD implementation? Is there any way out of this?
>> Like
>> > adding "anyone else" to allow-query structure?
>>
>> No, it's not missing:
>>
>> # grep blackhole named.conf
>> blackhole { clients; };
>> # named-checkconf ./named.conf
>> #
>>
>>
>> Philip Guenther
