little DNs question
SilverLeif
silverleif at infoave.net
Fri Aug 6 14:44:52 UTC 1999
I set my ttl to one hour.
At the top of my zone file very top i added in $TTL 1h
this has fixed this warning I think you can use $TTL 1d
and this should fix your problem
On 21 Jun 1999 10:28:00 -0700, Benjamin John
<bjohn at firstconsulting.net> wrote:
>Jun 18 17:37:04 omega named[339]: cache zone "" (IN) loaded (serial 0)
>Jun 18 17:37:04 omega named[339]: Zone "0.0.127.in-addr.arpa" (file
>named.local)
>: No default TTL set using SOA minimum instead
>Jun 18 17:37:04 omega named[339]: master zone "0.0.127.in-addr.arpa"
>(IN) loaded
> (serial 1999033020)
>Jun 18 17:37:04 omega named[339]: Zone "firstconsulting.net" (file
>db.firstconsu
>lting): No default TTL set using SOA minimum instead
>Jun 18 17:37:04 omega named[339]: master zone "firstconsulting.net" (IN)
>loaded
>(serial 1999033022)
>Jun 18 17:37:04 omega named[339]: Zone "88/29.92.220.209.in-addr.arpa"
>(file db.
>209.220.92): No default TTL set using SOA minimum instead
>Jun 18 17:37:04 omega named[339]: master zone
>"88/29.92.220.209.in-addr.arpa" (I
>
>
>I get this message about no default TTL
>here's my db files
>
> UW PICO(tm) 3.5 File: db.firstconsulting
>
>@ IN SOA ns.firstconsulting.net. root.firstconsulting.net. (
> 1999033022 ; Serial
> 10800 ; Refresh after 3 hours
> 3600 ; Retry after 1 hour
> 604800 ; Expire after 1 week
> 86400 ) ; Minimum TTL of 1 day
>
> UW PICO(tm) 3.5 File: db.209.220.92
>
>88/29.92.220.209.in-addr.arpa. IN SOA ns.firstconsulting.net.
>root.firstconsulting.net. (
> 1999033027 ; Serial
> 10800 ; Refresh after 3 hours
> 3600 ; Retry after 1 hour
> 604800 ; Expire after 1 week
> 86400 ) ; Minimum TTL of 1 day
>
>any ideas why it gives the TTL error ?
>
>Thanks
>
>
More information about the bind-users
mailing list