As I understand AUTHORITATIVE trumps anything. For example, from an inside
intranet name server forward the root (".") to somewhere on your edge, sprinkle
in a few internal-only authoritative zones, and enjoy. This is certainly not
the only choice, but it functions pretty well.
Len
>________________________________
> From: Jonathan Reed <cronst...@gmail.com>
>To: bind-users <bind-users@lists.isc.org>
>Sent: Sunday, June 2, 2013 12:10 PM
>Subject: does zone trump forward?
>
>
>
>I've only ever come across bind configs where forwarding is in place to locate
>certain zones, then all other queries are handled by either recursion or
>authoritatively. But what about the other way around, where I'm master for a
>few zones but forward the rest? Consider this:
>
>
>view "the-internet" {
> recursion no;
> type forward;
> forwarders { 8.8.8.8; };
> zone "example.com" {
>
> type master
> file "example.com"
> ......
>}
>
>
>Whats confusing me is the implied configuration setting of forward first when
>the forward statement is used. If it truly forwards first, then I see an odd
>logical scenario happening. All queries are sent to the forwarder before being
>handled by localhost. Then, once the forwarder recognizes that I'm the master
>of example.com, why would a loop not occur if the forwarder matches this view?
>To ask the question another way, does the zone statement take precedence on
>matching queries over any forwarding?
>
>
>Thanks
>_______________________________________________
>Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
>from this list
>
>bind-users mailing list
>bind-users@lists.isc.org
>https://lists.isc.org/mailman/listinfo/bind-users
>
>
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users