Re: Confused about my home networking setup
- From: Allodoxaphobia <bit-bucket@xxxxxxxxxx>
- Date: 11 May 2006 18:39:14 GMT
On Wed, 10 May 2006 19:35:50 -0600, Hamad bin Turki Salami wrote:
Allodoxaphobia wrote:
On Wed, 10 May 2006 10:43:15 -0600, Hamad bin Turki Salami wrote:
Life used to be simple. I used to assign a static id in the 192.168.1.x
range to every box on my home LAN and I used two static id's for my
domain name server from my ISP, Comcast.
Then I got a message from Comcast, warning that I needed to change my
network settings to use DHCP and automatically get the dns
from the provider. That's when things started going haywire.
Which I ignored -- and nothing untoward happened here.
I let them assign whatever IP addy they want to the cable modem.
I use a set of DNS IP's that are _not_ Comcast's -- both before and
after their 'dramatic' changes.
I run a LAN with 2 linux boxen, 2 OS/2 boxen, and my First Wife's
WinXP box -- using fixed LAN IP assignments.
Like I said, I received their dire warning -- ignored it -- and nothing
untoward happened here.
<offtopic>
Still running OS/2, huh? I used to run OS/2 until work commitments
forced me to start running Linux. At the time, Linux and OS/2 didn't
play well together on my PC and I had to drop OS/2. Has OS/2 changed
much in the past 5 years?
Not much - in my estimation. There hasn't been much from IBM except
for bug fixes beyond something like Warp 4.52. There's quite a bit
of porting of open linux software. There is still some 'activity'
in the comp.os.os2... ng's -- but maybe 50% is trolling and baiting.
I don't often fire up either of my OS/2 boxen. But, it feels good
to know that they are there. :-)
</offtopic>
I ignored Comcast's warning too. My router was already getting its
address by DHCP, and I thought there would be no sense to their chaning
the address of their dns server. Then one day I woke up and none of
my machines could find Yahoo or Google or Ebay ... So I started
switching over. I guess I could have just found another dns server,
like you have. But there should be an advantage to running a dns server
on my home LAN anyway, in terms of speed, right?
Maybe a cache'ing DNS.
My approach was to Google around for references/pointers to DNS IP's.
(Googling both the web and usenet.)
Then I tested response time (ping) and routing (traceroute) and picked
the 3 I thought looked best and dropped them into /etc/resolv.conf --
pointedly *not* selecting a Comcast DNS (whose servers, interestingly,
did not make to the Top Three, anyway.)
Being paranoid, I'd think that _if_ Comcast wanted to track where their
customers are going, they would trap that information at the DNS query
-- rather than on each passage of a packet.
As for Carnivore and The Department Of Homeland Hysteria, on the other
hand, .........
Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
38.24N 104.55W | @ config.com | Jonesy | OS/2
*** Killfiling google posts: <http//jonz.net/ng.htm>
.
- References:
- Confused about my home networking setup
- From: Hamad bin Turki Salami
- Re: Confused about my home networking setup
- From: Allodoxaphobia
- Re: Confused about my home networking setup
- From: Hamad bin Turki Salami
- Confused about my home networking setup
- Prev by Date: Re: How to find IPs of all machines in a lan
- Next by Date: Re: shutdown windows from linux
- Previous by thread: Re: Confused about my home networking setup
- Next by thread: Routing via (from) webinterface
- Index(es):
Relevant Pages
|
