On Tue, 2007-12-04 at 22:26 -0500, Chris Knadle wrote: > Rather than remove the 'search' line I recommend changing it to: > domain myhome.westell.com > nameserver 68.237.161.12 > nameserver 71.250.0.12 > > So instead of searching on a non-existant domain which may delay DNS > queries, this SETS what domain the box is in, giving you the same speedup. > Have a quick look at 'man resolv.conf' which will explain a bit more about > the options for the file. > > -- Chris > Regarding your suggested changes to /etc/resolv.conf: I was not previously aware that a necessary step in converting to static IP is to manually edit /etc/resolv.conf. I wonder where the GUI stored the DNS server addresses I gave it.
I did a search in Google books of "resolv.conf". From "Linux Administration Handbook" p420 (chapter on DNS): "Earlier versions of BIND used the "domain" directive in resolv.conf instead of the "search" directive.....We recommend replacing "domain" directives with "search" directives. So, it's clear to me that I should put the DNS server addresses in /etc/resolv.conf. It's not clear at this time that the "domain" line is the right way to go. On my most recent connection loss, I issued "service network stop" instead of "service network restart". The message "shutting down interface eth0" was displayed, the eth0 monitor on gkrellm disappeared, and then the command hung. So my next troubleshooting step is to find out where in "service network stop" the hang occurs. I viewed the script of the "service network" command and I don't understand the code. Although I've been reading "Advanced Bash Scripting Guide", I expect it will be a while before I understand the "service network" script. If you have access to the Fedora scripts, could you possibly direct me to the first script invoked by "service network stop" in which I should place an "echo" statement? As you suggested, I would proceed one script at a time, rather than using the "Bit Twister" approach of instrumenting all the scripts at once. I was not aware that iptables and/or Firestarter can dynamically change rules upon occurrence of undesired connection attempts. Could you suggest a Google search term I could use to find out more about this? I posted to the dslreports.com Verizon forum about the numerous connection attempts to port 80 I'm getting. I got a reply from one of the forum regulars. He says Verizon isn't strict about enforcing the no-server rule, so he doubts that is what I'm getting. He has no idea as to what it might be. _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Dec 5 - Open Source Show and Tell Jan 2 - TBD Feb 6 - DBUS Mar 5 - Setting up a platform-independent home/small office network using Linux
