VanLUG Email Archive
> I looked through that rfc but it had no rational included.
> Can someone convince me that settting your dns
> with pppd is a good thing(I know it's
> a usefull thing to some ppl)?
address of a name server then it's automatically propagated to those
customers using the feature, possibly cutting down phone calls
considerably.
> I don't believe setting up application lvl software
> belonghs in the datalink/network layer(s).
Pppd is application software that sets up and maintains the link
level. Why shouldn't it start up an application level script or edit
a config file itself based on information it's negotiated with the
other end?
My opinion is slightly biased against it doing so simply because I've
always believed resolv.conf is a file for humans, but OTOH it can be
thought of as a cool hack to automatically maintain resolver settings.
One could argue that RFC 1877 is incomplete because it only addresses
name server IP addresses. What about all the other info needed to
configure a resolver?
> And yes I'm not too fond of defaultroute either.
Without a default route your routing table would be *very* large.
There're about 50k routes on the net these days.
-- Toomas Losin ParaLynx Internet
New Westminster, BC