No subject

[Peter.Koenig at gmx.de]

Hi,

we have a quite particular setup:

Part of a department "adepartment" in our domain adomain.com is
protected by a firewall. The DNS for adomain.com including
adepartment.adomain.com is not maintained by us. The hosts behind the
firewall are not listed in the public dns.

So we would like to set up a DNS-server (internal DNS) behind our
firewall. Our wishes for a setup are as follows:

1. Hosts protected by the firewall should be able to resolve other hosts
behind the firewall as well as all other hosts in
adepartment.adomain.com
2. This should be possible without having to include all of the data for
adepartment.adomain.com in our internal DNS-server.
3. We would like to achieve this without having to give up our flat
namespace for adepartment.adomain.com, i.e. not introducing subdomains.

So the setup should be as follows:

The internal DNS should:
1. Try to resolve queries for adepartment.adomain.com or forward them to
the public DNS in case the name cannot be resolved. Regulary the DNS
returns a NOERROR at this point.
2. Forward all other requests (i.e. not including
adepartment.adomain.com) to the public DNS.

If I understood P. Albitz' and C. Liu's "DNS and Bind" correctly this
could be realised using "views" in the upcoming Bind 9.x release. 

Can anybody give me a hint to solve this problem with standard Bind 8.x
?

Thanks
Pete

-- 
Sent through GMX FreeMail - http://www.gmx.net