Problems with default ttl

[Kevin Darcy]

I guess it's time for the old boilerplate again:

> Put a $TTL directive at the top of your master files. It takes an
> argument of how long the default TTL for the zone should be: you can
> either use a plain number, which is interpreted as seconds, or numbers
> combined with letters signifying time units, e.g. "1d" = 1 day = "86400"
> (seconds).
>
> Or, alternatively, if you want your default TTL to be the same as your
> negative caching TTL (the last field of the SOA record), then just
> ignore the warnings, since that's what named will use in the absence of
> a $TTL directive anyway, as it was used to prior to RFC 2308.
>

- Kevin

Guillermo Villasana Cardoza wrote:

> Hello everyone...
> I am having the following error beeing logged... and I don't know why:
> Zone "0.0.127.in-addr.arpa" (file db.127.0.0): No default TTL set using
> SOA minimum instead
>
> my file is: db.127.0.0 and is configured as follows:
>
> ; Archivo db.127.0.0
> @ IN  SOA dns.oficinas.conalep.edu.mx. soporte.conalep.edu.mx. (
>         2000083100      ; Serial AAAAMMDDnn
>         3600            ; Actualiza despues de 1 hora
>         600             ; Reintenta despues de 1 minuto con 10 segundos
>         432000          ; Expira despues de 5 dias
>         1800 )          ; Servidor remoto debe mantener 30 minutos en
> cache
>
> @  IN  NS  dns.oficinas.conalep.edu.mx.
>
> 1.0.0.127.IN-ADDR.ARPA.         IN  PTR   localhost.
>
> ;Fin Archivo db.127.0.0
>
> Thanks
> Guillermo Villasana