Thanks for your advice.
I'm trying to set up `forward only` DNS, according to the guide of
SSLUG page and DNS-HOWTO(Chap 8.6 refers to forward nameserver).
There's a problem occurred.
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
>17:11:26 fmv named[373]: master zone "local" (IN) loaded (serial 1997022700)
>17:11:26 fmv named[373]: Zone "0.0.127.in-addr.arpa" (file named.rev-local): No
>default TTL set using SOA minimum instead
>17:11:26 fmv named[373]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial
>199909220)
>17:11:26 fmv named[373]: Zone "localdomain" (file named.localdomain): No default TTL
>set using SOA minimum instead
>17:11:26 fmv named[373]: master zone "localdomain" (IN) loaded (serial 199901121)
>17:11:26 fmv named[373]: Zone "0.168.192.in-addr.arpa" (file named.rev-localdomain):
>No default TTL set using SOA minimum instead
>17:11:26 fmv named[373]: master zone "0.168.192.in-addr.arpa" (IN) loaded (serial
>199901121)
>17:11:26 fmv named[373]: listening on [127.0.0.1].53 (lo)
>17:11:26 fmv named[373]: listening on [192.168.0.9].53 (eth0)
>17:11:26 fmv named[373]: Forwarding source address is [0.0.0.0].1024
>17:11:26 fmv named: named startup succeeded
>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
>17:11:27 fmv diald[388]: Using fifo /etc/diald/diald.ctl
>17:11:27 fmv diald: diald startup succeeded
>17:11:27 fmv diald[388]: Proxy device established on interface tap0
>17:11:28 fmv diald[388]: Diald initial setup completed.
>17:11:28 fmv lpd: lpd startup succeeded
>...
>...local configuration...
>...
>17:11:33 fmv rc: Starting local succeeded
>17:11:53 fmv PAM_pwdb[470]: (login) session opened for user root by LOGIN(uid=0)
>17:11:56 fmv diald[388]: Trigger: udp 192.168.0.254/1024 203.140.1.10/53
Another log:
>17:11:28 fmv diald[388]: Diald initial setup completed.
>17:11:56 fmv diald[388]: filter accepted rule 1 proto 134633600 len 45 packet
>192.168.0.254,1024 => 203.140.1.10,53
>17:11:56 fmv diald[388]: Trigger: udp 192.168.0.254/1024 203.140.1.10/53
>17:12:26 fmv diald[388]: filter accepted rule 1 proto 134633600 len 45 packet
>192.168.0.254,1024 => 203.140.10.10,53
>17:12:56 fmv diald[388]: filter accepted rule 1 proto 134633600 len 45 packet
>192.168.0.254,1024 => 203.140.1.10,53
>17:13:26 fmv diald[388]: filter accepted rule 1 proto 134633600 len 45 packet
>192.168.0.254,1024 => 203.140.10.10,53
Frank Damgaard <[EMAIL PROTECTED]> wrote:
...
>This part is if you don't use diald, but manually connect to the internet
>with some ppp-on/usernet/kppp ......
...
>But if you use diald the best is to use a caching/forwarding nameserver
I see.
There are several ways to deal with `resolving hostname` ,and forwarding
nameserver is best, maybe?
--
Sagami
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
