Forward by zone...

[Mark_Andrews at isc.org]

> 
> Fine, You win  
> This is extactly what we have in PRODUCTION
> 
> options {
>         directory "/var/named";
>         forward only;
>         forwarders {
>                 192.168.31.11; 192.168.31.80; 192.168.31.81;
>         };
>         check-names slave ignore;
>         dump-file "/var/tmp/named_dump.db";
>         statistics-file "/var/tmp/named.stats";
>         memstatistics-file "/var/tmp/named.memstats";
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>         // query-source address * port 53;
> };
> 
> zone "sweet.dude.com" {
>         type forward;
>         forward only;
>         forwarders { 172.26.11.100; }; //SERVER B 
> };
> 
> zone "dude.com" {
>         type master;
>         file "fwd/dude.com";
>         also-notify { 192.168.31.89; 192.168.4.88; 192.168.4.89;
> 192.168.45.88; 192.168.45.89; };
> };

	This configuration will not work unless there is a delegating
	NS RRset for sweet.dude.com in dude.com.

	Without the NS RRset you are telling the server to do to
	answer questions for sweet.dude.com in two different ways
	and the contents of the dude.com zone win (sweet.dude.com
	does not exist).

	Now there are a number of ways to solve this but we need to
	know what you are trying to achieve.

	Is this version of dude.com only visible to internal machines?
	Who do you want to know about sweet.dude.com?
	Are you just trying to override the global forwarding for
	internal subdomains?

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org