On Mon, 5 Feb 2001, Flip ter Biecht wrote:
> >I downloaded lsppp, but I'll need some time to get it to work. Just
> >invoked after miniterm, it can't find a carrier.
>
> Work done... What a splendid configuration tool, but how can it find the
> DNS on it's own?
I've never used lsppp, so I'm not sure what you're asking, but
anyone running an ISP has the option (and I daresay ALL do these
days) to enable sending the DNS address as a part of the ppp
negotiations.
>From the pppd man page:
ms-dns <addr>
If pppd is acting as a server for Microsoft Windows
clients, this option allows pppd to supply one or
two DNS (Domain Name Server) addresses to the
clients. The first instance of this option speci
fies the primary DNS address; the second instance
(if given) specifies the secondary DNS address.
(This option was present in some older versions of
pppd under the name dns-addr.)
This option is also available for Linux clients. If you wish,
you can allow the ISP to over-write your resolv.conf file each time
you login. This wouldn't be very helpful if you're running your
own DNS server though!
Even with that option disabled (client-side), the ISP still sends
the DNS for you to ignore... ;-)
Here's a section of my /var/log/messages that shows part of
the ppp transactions:
Feb 4 21:25:08 localhost pppd[11206]: Serial connection established.
Feb 4 21:25:08 localhost pppd[11206]: Using interface ppp0
Feb 4 21:25:08 localhost pppd[11206]: Connect: ppp0 <--> /dev/modem
Feb 4 21:25:28 localhost kernel: PPP BSD Compression module registered
Feb 4 21:25:28 localhost kernel: PPP Deflate Compression module registered
Feb 4 21:25:28 localhost pppd[11206]: local IP address 162.42.141.113
Feb 4 21:25:28 localhost pppd[11206]: remote IP address 162.42.141.126
Feb 4 21:25:28 localhost pppd[11206]: primary DNS address 162.42.150.33
Feb 4 21:25:28 localhost pppd[11206]: secondary DNS address 162.42.150.47
- Steve
