Thanks Timothy by your help. Searching Dejanews, I found the answer:
To avoid "No default TTL set using SOA instead" message in you
/var/adm/messages (and console) everytime you restart your named daemon,
set the default TTL (it makes sense, no??? :-) in the first line og
each zone file:
Just do it.
Christian Pinheiro wrote:
> Hi there,
> Every time we restart our DNS daemon, the named logs on
> /var/adm/messages the follow messages:
> Aug 23 18:18:29 lynx named: Zone "veritelnet.com.ar" (file
> virtual/veritelnet.com.ar): No default TTL set using SOA minimum instead
> Aug 23 18:18:29 lynx named: Zone "193.230.200.in-addr.arpa" (file
> named.rev): No default TTL set using SOA minimum instead
> Aug 23 18:18:29 lynx named: Zone "0.0.127.in-addr.arpa" (file
> named.local): No default TTL set using SOA minimum instead
> this is one of my conf files:
> @ IN SOA servername.veritel.com.br.
> 1999081002 ; serial number
> 10800 ; refresh after 3 hours
> 3600 ; retry after 1 hour
> 604800 ; expire after 1 week
> 3600 ) ; minimum TTL of 1 day
> IN NS ns3.veritel.com.br.
> IN NS ns2.veritel.com.br.
> servername IN A xxx.xxx.xxx.xxx
> But all appears to be running ok. I know there may have one place to
> setup a default TTL, but where? I read the DNS&BIND book (O'Reilly and
> Assoc), and the only tip I found is to use one TTL for each record. But
> it's very strange, because we had ever used the same conf files, and
> nothing appeared on our console.
> Does anybody can help me with this, please?
> Thanks in advance
> Christian Pinheiro
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:25 CDT