From: "Carl Gehr" Received: from [192.168.100.201] (account carl.gehr@mcgcg.com HELO localhost) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.3) with ESMTPA id 1903880 for ecs-t6x@2rosenthals.com; Fri, 30 May 2008 20:59:05 -0400 To: "eCS ThinkPad T60/61 Mailing List" Date: Fri, 30 May 2008 20:58:53 -0400 (EDT) Reply-To: "Carl Gehr" Priority: Normal X-Mailer: PMMail 2.20.2382 for OS/2 Warp 4.5 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [eCS T60/T61] Installed eCS 2.0 RC4 on T61 (6465-CTO) withSUSE SLED 10 preloaded. Message-ID: On Fri, 30 May 2008 17:02:46 -0700 (PDT), Jon Harrison wrote: >On Fri, 30 May 2008 16:00:57 -0400 (EDT), Carl Gehr wrote: > >> Each new location [i.e., ISP] has their own DNS. >> Getting to the DNS that each location needed to find everything else >>has been a mess when the RESOLV2 file is overwritten. > >You raise a good point. I have not yet traveled with the TP61 so >had not thought much about it. I'm interested in the 4.2.2.3 tip. >Is that just a random known dns server? I have a TLD ip address as >the 3rd entey in my resolv2 but I have no idea if it ever gets >queried. As I got the complete tip from Lewis: "...4.2.2.1, 2, & 3 work well. They're old GTE servers, and are fairly responsive..." FWIW, it also appears that the sequence of the NameServer statements may [but should not be] significant. In the cases I mentioned, it seems that the DNS built into the DSL router has to be first. I put 4.2.2.3 next, followed by my own ISP's DNS IPs. If I hit a situation where a name cannot be resolved, I'll remove the Read-Only, add it to the list, reset to Read-Only and go from there. This all said, I'm not claiming I know why this is working well. But, I'll keep doing it as long as it works. [Thanks, again, to Lewis!] Carl