Well.. I've done some research... seems like named wants $TTL <time> in the
zone files... but can't I set thet globally somewhere? I got about 95
zonefiles... it's a hell to edit them all.
/ Rickard
On 22-Nov-99 Bois, Mathieu wrote:
>> Why does named dump this to syslog after I upgraded:
>> named[11471]: Zone "foobar.com" (file db.foobar.com): No
>> default TTL set
>> using SOA minimum instead
>
> Hi!
>
> I've began with Bind at version 8.x, so I don't know about old
> versions's configurations.
> Since 8.2.x, they seem to have put more control over the syntax of
> the config files.
> It appeared to me that I ran since the beginning with buggy files
>:-) and that was a little hard to upgrade to 8.2.x because I didn't noticed
> that before.
> But, as you, I also have got the same warning message. This is a new
> warning that didn't exist at all in bind prior to 8.2.something.
> I'm running my bind with this warning without problem. There is
> maybe a field Time To Live to add somewhere in the zone config file, but
> I've not look for it. And by the way, maybe is it a little bug, since they
> introduced a lot in the new version, that were far more serious than that.
>
>> I have converted named.boot to named.conf and that went smooth.
>> Afaik the db.* files hasn't changed or?
>>
>> This is the begining of the db.* files:
>> @ IN SOA ns.foobar.org. hostmaster.foo.org. (
>> 1999091301 ; serial [yyyyMMddNN]
>> 21600 ; refresh [6h]
>> 3600 ; retry [1h]
>> 691200 ; expire [8d]
>> 86400) ; minimum [1d]
>
> As far as I remember (from all the docs I read when I first began
> DNS settings), the zone files have the same syntax as before.
> And you can put straightly 6h, 1h, 8d, 1d instead of the time in
> seconds : Bind 8.2.x recognizes it.
>
> Hope this helps
>
> Mathieu
Rickard �berg <[EMAIL PROTECTED]>
"Why do you necessarily have to be wrong just because a few
million people think you are?"
