TTL default problem?
john at webfreebees.net
Sun Nov 7 12:00:04 UTC 1999
On 5 Nov 1999 15:41:57 -0800, Barry Margolin <barmar at bbnplanet.com>
>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: Zone "lightsign.com" (file
>>ign.com): No default TTL set using SOA minimum instead
>>this is the record for that zone:
>>@ IN SOA ns.lightsign.com.
>> 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 184.108.40.206
>>ns IN MX 10 mail
>>www IN CNAME mail
>>ftp IN CNAME mail
>>mail IN A 220.127.116.11
>>mail IN MX 10 mail
>>mhutch IN A 18.104.22.168
>>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?
More information about the bind-users