[sllug-members]: DHCP & DNS Issues

[Elijah Newren]

On 6/16/06, Justin R Findlay <justin at jfindlay.us> wrote:
> Although it feels like a hack you could put
>
> route add default gw 192.168.0.1
>
> in /etc/rc.local.  A real redhat and/or DHCP guru would be capable of
> giving you a real answer here.

Interesting, but doesn't this assume she only uses her laptop on a
network where the gateway is 192.168.0.1?  That is only true of her
connection at home.

> I've had problems with qwest provided routers acting as nameservers.  My
> solution so far was to move the entry for the real nameserver to the top
> of the file and then save it as
> /etc/resolv.conf.the_real_thing_not_the_one_the_stupid_qwest_router_misconfigured
> and then again put something in /etc/rc.local like:
>
> cp -f /etc/resolv.conf.blah_blah /etc/resolv.conf
>
> My guess is that when you have the wrong nameserver at the top it has to
> timeout somehow before moving on to the next one in the list.

Yes, I guess I could just hardcode /etc/resolv.conf with a list of
nameservers known to be usable enough from all the different network
connections (school, home, etc.) and I've done that before, but if the
nameservers I pick get decomissioned or moved or whatever (which has
also happened before) then /etc/resolv.conf needs to be edited again.
That's fine for me, but the issue came up because this also affects my
sister now.  I kind of dislike using this kind of workaround that I
feel is likely to fail for her some months down the road, and would
prefer getting dhcp to actually work like it's supposed to (or as
close as possible to it), if feasible with a reasonable amount of
effort.

Thanks for your comments.  :)

Elijah