Toru SAGAMI wrote:
....
> At boot time, when diald starts after named started ,at that point
> there seems to be no problem -- named's log shows a following line but
> a log in your SSLUG page has same line,so I think this is not a problem.
> >sysquery: sendto([203.140.1.10].53): Network is unreachable
>
> After that, diald is going to dial to my ISP every 30 second.
>
> Any configuration missing ? I don't know what to do with this.
>
>
> Here's a log:
> >17:11:25 fmv named[373]: starting. named 8.2.1 Fri Sep 24 14:52:24 EDT 1999
>^[EMAIL PROTECTED]:/usr/src/bs/BUILD/bind-8.2.1/src/bin/named
> >17:11:26 fmv named[373]: hint zone "" (IN) loaded (serial 0)
> >17:11:26 fmv named[373]: Zone "local" (file named.local): No default TTL set using
>SOA minimum instead
there seems to be some syntax errors. Try adding some debug to bind (-d[N] )
The line number(s) with errors should show.
TTL = Time To Live value is missing ?
This is the last number in the SOA record.
...
> >17:11:26 fmv named[374]: Ready to answer queries.
> >17:11:26 fmv named[374]: sysquery: sendto([203.140.1.10].53): Network is unreachable
It seems there is not route to 203.140.1.10 ?
...
> I see.
> There are several ways to deal with `resolving hostname` ,and forwarding
> nameserver is best, maybe?
Yes. But using a caching nameserver with analog modem og 64K ISDN
will safe some time when making several DNS lookups to same address.
--
mvh Frank Damgaard [EMAIL PROTECTED] | [EMAIL PROTECTED] |fido 2:236/15.2
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
