forwarding on zone base does'nt work; again

Kevin Darcy kcd at daimlerchrysler.com
Thu Jan 13 17:33:08 UTC 2000


Barry Finkel wrote:

> Thomas Stalder <tom at coco.ch> wrote:
>
> >I'm running Bind 8.2.2-P5 on a Sun Ultra 5, with Solaris 7.
> >Configured as master for a few 'internal' domains and slave for
> >a few more 'internal' domains. This works fine so far.
> >I tried to set up a forwarder for another internal domain,
> >which does not allow zone transfers.
> >
> >This does not work. I get following:
> >
> >Jan 12 15:49:12 dns001 named[164]: reloading nameserver
> >Jan 12 15:49:12 dns001 named[164]: /etc/named.conf:59: syntax error near forward
> >Jan 12 15:49:12 dns001 named[164]: no type specified for zone 'firm-internal.com'
> >Jan 12 15:49:12 dns001 named[164]: zone 'firm-internal.com' did not validate, skipping
> >Jan 12 15:49:12 dns001 named[164]: /etc/named.conf:64: syntax error near '}'
> >Jan 12 15:49:12 dns001 named[164]: Ready to answer queries.
> >
> >
> >That's how the it looks in the named.conf file:
> >
> >zone "firm-internal.com" in {          //  <- line 58  (my comments)
> >       type forward;
> >       forward only;
> >       forwarders {
> >       10.41.8.91;                             //  <- Intranet  Name Server
> >       };
> >};
>
> My reading of the BIND book (3rd edition) shows that in line 58 you
> need parentheses surrounding the string "in":
>
>      zone "firm-internal.com" (in) {

Where do you get that from? All of the configuration examples in the book use "in" without
parentheses. It doesn't parse properly with the parentheses. I have configured a test zone
with exactly the same syntax as the original poster, and my 8.2 named can parse it just
fine. So I don't think it's a syntax problem.


- Kevin




More information about the bind-users mailing list