Re: BIND 9 views, secondary + lame messages

Sorry for replying to my own post, but I think I have a decent solution. I
actually saw it in some other current messages in this group. I have used
the include directive in both views to include the zones with identical data
(in each view). Now my zones that I secondary for folks out on the net show
up internally with authoritative answers.

In article <bf73kd$2lii$1@sf1.isc.org>, vom wrote:
> Running BIND 9, external and internal views configured. I am secondarying
> some zones within the external container and they are working fine (aa flag
> to external clients). However since one of the listed NS servers in the
> seconary'ed zones is my server, it's A record comes off the internal view.
> The internal view doesn't give an auth answer because the slave zone is
> configured in the external view. Therefore the server logs a
> lame-delegation since the listed NS (internal) is giving a non-auth answer.
>
> What is the best practice to handle this ? I was thinking of just adding
> the slaved zones to the internal view, but then:
>
> 1) Would the zones get pulled twice ?
> 2) I don't like the idea of maintaining them in both views.
>
> Any insight or advice would be appreciated. Thanks.
>


--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
7407 DC86 AA7B A57F 62D1 A715 3C63 66A1 181E 6996
"SH1-0151. This is the serial number, of our orbital gun."