I should have posted this question two weeks ago. You are absolutely right.

Thanks


David Botham wrote in message news:...
> bind-users-bounce@isc.org wrote on 10/04/2004 12:25:51 AM:
> > When this message appeared in /var/log/messages, I removed lines in
> > the named.conf until it is barebones but the error persists. How do I
> > determine what is being referenced as '4'?
> >
> > ---------/var/log/messages---------
> > starting BIND 9.2.3 -u named -t /var/named/chroot

>
> I noticed that you are running named in a chroot jail. What is the
> absolute path of the named.conf file below?
>
> If it is /etc/named.conf and not /var/named/chroot/etc/named.conf then you
> are editing the wrong file.
>
> You should be editing /var/named/chroot/etc/named.conf.
>
>
> Thanks,
>
>
> Dave...
>
>
> > using 1 CPU
> > named startup succeeded
> > loading configuration from '/etc/named.conf'
> > /etc/named.conf:2: expected prefix length near '4,'
> > loading configuration: unexpected token
> > exiting (due to fatal error)
> > ---------/etc/named.conf------------
> > // generated by named-bootconf.pl
> >
> > options {
> > directory "/var/named";
> > // query-source address * port 53;
> > };
> >
> > //
> > // a caching only nameserver config
> > //
> >
> > controls {
> > inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> > };
> >
> > include "/etc/rndc.key";
> >
> > zone "." {
> > type hint;
> > file "named.ca";
> > };
> > zone "0.0.127.in-addr.arpa" {
> > type master;
> > file "named.local";
> > };
> >
> > Thank
> > Benu
> >