TTL default problem?

[john]

On 5 Nov 1999 15:41:57 -0800, Barry Margolin <barmar at bbnplanet.com>
wrote:

>In article <38230db4 at news.cadvision.com>, M & J <mhutch at cadvision.com> wrote:
>>This is the /var/log/messages
>>
>>Nov  5 09:55:45 icheeranddance named[2825]: Zone "lightsign.com" (file
>>pz/lights
>>ign.com): No default TTL set using SOA minimum instead
>>
>>this is the record for that zone:
>>
>>@               IN      SOA     ns.lightsign.com.
>>mhutch.icheeranddance.ne
>>t. (
>>                        1999110311      ; serial
>>                        86400           ; refresh
>>                        7200            ; retry
>>                        3600000         ; expire
>>                        172800 )        ; default_ttl
>>
>>@               IN      NS      ns.lightsign.com.
>>@               IN      MX      10      mail.lightsign.com.
>>localhost               IN      A       127.0.0.1
>>ns              IN      A       207.228.97.225
>>ns              IN      MX      10      mail
>>www             IN      CNAME   mail
>>ftp             IN      CNAME   mail
>>mail            IN      A       207.228.97.236
>>mail            IN      MX      10      mail
>>mhutch          IN      A       207.228.97.236
>>
>>Do you see any problems in it?
>
>You don't have a $TTL directive to set the default TTL.  Since BIND 8.2,
>the last parameter to the SOA record is the negative cache TTL, not the
>default TTL.  The comment "; default_ttl" doesn't change that.


I get the same error upon starting named (not when reloading).

I have the same setup, although the comment is different (as if that
will make any difference).

My question is, how to fix this?