(BIND) Problem with configuration files

[Kevin Darcy]

Then I have no clue. I was only able to reproduce that sequence of errors by
putting control characters directly after the refresh, retry, expire and
negative-caching-TTL (formerly minimum TTL) fields of the SOA record.

Is this the *only* zone file which is giving these kinds of errors? If so,
then what can you think of that's different about it?


- Kevin

Eelko de Groot wrote:

> I made a hexdump of the file and I did not find any unprintable control
> characters.
>
> Any other suggestions?
>
> Eelko
>
> > -----Oorspronkelijk bericht-----
> > Van: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]Namens
> > Kevin Darcy
> > Verzonden: dinsdag 19 december 2000 1:48
> > Aan: bind-users at isc.org
> > Onderwerp: Re: (BIND) Problem with configuration files
> >
> >
> >
> > Check for unprintable control characters in the zonefile,
> > especially after each
> > of the numeric values of the SOA.
> >
> >
> > - Kevin
> >
> >
> > Eelko de Groot wrote:
> >
> > > Hi,
> > >
> > > I try to setup BIND on my local (test) network but when I
> > startup named I
> > > get warnings in the syslog.
> > >
> > > For example, my db.127.0.0 file looks like:
> > > __________________________________________________________________
> > > 0.0.127.in-addr.arpa. IN SOA cse3.intern. efdegroot.csnet.nl. (
> > >                2000121501 ; Serial
> > >                10800      ; Refresh after 3 hours
> > >                3600       ; Retry after 1 hour
> > >                604800     ; Expire after 1 week
> > >                86400 )    ; Minimum TTL of 1 day
> > > ;
> > > ; Name servers
> > > ;
> > > 0.0.127.in-addr.arpa. IN NS cse3.intern.
> > >
> > > ;
> > > ; Addresses point to canonical name
> > > ;
> > > 1.0.0.127.in-addr.arpa.  IN PTR  localhost.
> > >
> > > __________________________________________________________________
> > >
> > > And in syslog I get the following messages:
> > > __________________________________________________________________
> > >
> > > Dec 18 15:24:09 cse3 named[24903]: Zone "0.0.127.in-addr.arpa" (file
> > > db.127.0.0): No default TTL set using SOA minimum instead
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0:2: expected a
> > TTL, got "10800"
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0:3: expected a
> > TTL, got "3600"
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0:4: expected a TTL, got
> > > "604800"
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0:5: expected a
> > TTL, got "86400"
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0: WARNING SOA
> > expire value is
> > > less than SOA refresh+retry (600 < 600+600)
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0: WARNING SOA
> > expire value is
> > > less than refresh + 10 * retry (600 < (600 + 10 * 600))
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0: WARNING SOA
> > expire value is
> > > less than 7 days (600)
> > > Dec 18 15:24:09 cse3 named[24903]: db.127.0.0: WARNING SOA
> > refresh value is
> > > less than 2 * retry (600 < 600 * 2)
> > > Dec 18 15:24:09 cse3 named[24903]: master zone
> > "0.0.127.in-addr.arpa" (IN)
> > > rejected due to errors (serial 2000121501)
> > > __________________________________________________________________
> > >
> > > What am I doing wrong?
> > >
> > > Regards,
> > > Eelko.
> >
> >
> >
> >
> >