error starting bind 9.1.1

[Roy Arends]

On Thu, 5 Apr 2001, Silvestre Malta wrote:

> Hello im tryng to upgrade my bind to bind 9.1.1
> but im having the folloing error ...
> 
> named[29625]: dns_master_load: db.xxxxxx:6: no TTL specified
> Apr  5 12:16:38 named[29625]: dns_zone_load: zone xxxxxx.xx/IN: loading master file db.xxxxxxx: no ttl
> 
> and here is the db.xxxxxxx file:
> 
> 
> ; BIND version named 8.1.2 Thu Sep 16 22:13:44 GMT 1999
> ; BIND version jkh at highwing.cdrom.com:/usr/obj/usr/src/libexec/named-xfer
> ; zone 'xxxxxxxxx.xx'   last serial 2000080401
> ; from 195.61.93.4   at Fri Sep  1 17:15:57 2000
> $ORIGIN xx.
> xxxxxx      IN      SOA     ns.xxxxxxx.xx. hostmaster.xxxxxxx.xx. (
>                 2000090101 3600 1800 604800 43200 )
>                 IN      NS      ns.xxxxxxx.xx.
>                 IN      NS      ns1.xxxxxxx.xx.
>                 IN      MX      10 mail.xxxxxx.xx.
>                 IN      MX      20 mail2.xxxxxxx.xx.
> $ORIGIN xxxxxxx.xx.
> www             IN      CNAME   www.xxxxxxx.xx.
> 
> 
> But i have TTL defined !!! it is a BOLD   
> can any one help me ???

from bind-9.1.1/doc/misc/migration:

2.1. Strict RFC1035 Interpretation of TTLs in Zone Files

BIND 8 allowed you to omit all TTLs from a zone file, and used the
value of the SOA MINTTL field as a default for missing TTL values.

BIND 9 enforces strict compliance with the RFC1035 and RFC2308 TTL
rules.  The default TTL is the value specified with the $TTL
directive, or the previous explicit TTL if there is no $TTL directive.
If there is no $TTL directive and the first RR in the file does not
have an explicit TTL field, the error message "no TTL specified" is
logged and loading the zone file fails.

To avoid problems, use a $TTL directive in each zone file.


Regards,
Roy Arends
Nominum