Catch ALL Setup

[Robert Stucke]

Just create your own root zone and add the wildcard entry in there.

zone "." in {
        type master;
        file "db.root";
        allow-update { None; };
        allow-query { Any; };
};


Rob



On Wed, Feb 18, 2009 at 9:50 AM, Sven Eschenberg <sven at whgl.uni-frankfurt.de
> wrote:

> The problem I am actually facing is, that I don't want to use it in a
> specific zone, but basicly in every imaginable zone. No matter which Query
> comes in, always respong with IP X.
>
> A normal wildcard setup for a specific zone is pretty obvious and straight
> forward.
>
> The search path wouldn't matter either, since all other domains should be
> looked up at the same DNS anyway. And even if clients were to try reaching
> any external subnet, they'd be out of luck.
>
> Regards
>
> -Sven
>
>
> Stacey Jonathan Marshall schrieb:
>
>> On 02/18/09 05:19, Mark Andrews wrote:
>>
>>>    $ORIGIN .
>>>    @ 0 SOA ...
>>>    @ 0 NS ...
>>>    * 0 A 1.2.3.4
>>>
>>>
>> Just be careful of what you wish for, don't come back here saying that
>> your resolver search path is no longer working ;-)
>>
>> To explain, lets say you use the above in example.com and configure
>> clients with 'search example.com another.com someother.com' in
>> resolv.conf. A resolver looking for 'test', hoping to find it as '
>> test.another.com' would query the name server for test.example.com first
>> and get back 'test.example.com IN A 1.2.3.4.'.
>>
>> regards,
>> Stacey
>>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090218/0c8cc309/attachment.html>