Re: Internet connection problem
From: Moe Trin (ibuprofin_at_painkiller.example.tld)
Date: 01/10/05
- Previous message: Doug Purdy: "Re: Sound Problem"
- In reply to: Tim: "Re: Internet connection problem"
- Next in thread: Stefan Patric: "Re: Internet connection problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 09 Jan 2005 17:12:21 -0600
In article <fxpzrnb21p4w$.pcuibgbyz5cn.dlg@40tude.net>, Tim wrote:
>It's quite common for ISPs to tell you what DNS server to use as you
>connect, some do rotate several of them amongst their users (I'm told) to
>spread the load around.
The 'tell you at connect time' is a function of the windoze philosophy of
minimizing the technical requirements of the user. Plug it in, and it just
magically works. This is also an advantage if you are moving your computer
from network to network (example, home to work, and vice-versa). It's often
considered a security problem (where have you _ever_ heard that about a
microsoft concept), as it's not under control of the user.
It's not very likely for the ISP to be playing "musical IP addresses" with
the DNS servers - as there really is some work needed to set up a server.
Once done, there is no reason to tear it down, and rebuild it again for a
whim. Load sharing is used, but DNS is not a CPU or bandwidth intensive task
(as compared to for example, a web server).
>A problem with that is the seemingly poor support for dynamic IPs with
>Linux (they're something that's been around for quite some time). If I
>configure my gateway box to use its own DNS server, the dialup connect
>script will often usurp it with the dynamically discovered ISP's DNS
>servers (rather than add them to the list, it puts them at the top).
That depends on the tool you are using to connect. For dialup, what you
are actually using is pppd and that definitely does NOT mess with
/etc/resolv.conf (see the man page). "Helper" tools like kppp may alter
/etc/resolv.conf, but that's easy to fix/prevent. (I put the word "Helper"
in quotes, because they also hinder as much as help, and tend to confuse
things.) If you are connecting via Ethernet (cable or DSL, but also for
many home network setups), the name server setup is controlled by the DHCP
server (meaning extra work for whoever set it up), and whatever client you
are using.
Very few of our systems ever move, so we spend the extra minute or so when
installing them to set them to static addresses. With RFC1918 (which replaced
RFC1597 from 1994) providing nearly 17.8 million usable IP addresses, the
original rational for DHCP (lots of computers, not many addresses - see
RFC0951 from 1985) hasn't existed for ten years. The only remaining reason
for it to exist is the consumer market where the user is almost always
lacking any technical knowledge, and depending on "expert" systems to make
up for it. But the expert systems are only as good as the person who set
them up.
Old guy
- Previous message: Doug Purdy: "Re: Sound Problem"
- In reply to: Tim: "Re: Internet connection problem"
- Next in thread: Stefan Patric: "Re: Internet connection problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
