-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Your server believes itself to be authoritative for foo.com and
everything under it, and therefore there is no need to forward. To
resolve this, add delegation records to foo.com:

lan1.foo.com. NS server.10.3.1.12.
lan2.foo.com. NS server.10.3.1.12.

Obviously, those names are all fake, including the names on the right
hand side. Replace them with correct values. Once you have these in
place, you may even find you don't need the forward zones at all - the
server may be able to follow the delegations down the namespace tree
as indicated. (You may need to add a "forwarders {};" line to your
foo.com zone statement, though.)

Chris Buxton
Professional Services
Men & Mice

On Sep 16, 2008, at 12:54 AM, ml@bortal.de wrote:

> Hello List,
>
> i have some problems with per domain forwarding.
> If i want to resolve pc1.lan1.foo.com then it does not ask the
> forwarders.
> But if i remove zone "foo.com", then it seems to work.
> Has anyone an idea why?
>
> Thanks,
> Mario
>
>
> zone "lan1.foo.com" IN {
> type forward;
> forwarders {10.3.1.12;};
> };
>
> zone "lan2.foo.com" IN {
> type forward;
> forwarders {10.3.1.12;};
> };
>
>
> zone "foo.com" {
> type master;
> file "mwk.de";
> };
>
>
>
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkjP5bIACgkQ0p/8Jp6Boi0hVQCZAfkkBNv57VrVhdg7VF3IWy+m
9vkAoJDVNcUc+KCxyb6Zzu+6CKsNshs5
=xDJ5
-----END PGP SIGNATURE-----