On 4/1/07, Paul Lussier <[EMAIL PROTECTED]> wrote:
; generated by /sbin/dhclient-script
nameserver 192.168.1.1
search localdomain
Interesting, mine looks like this:
A lot of SOHO routers run a DNS proxy, so you can just configure
your systems to use 192.168.1.1 as the resolver, and the router
forwards the requests to whatever the ISP DHCP servers are handing out
lately.
Which is not to say that the OP's router *is* doing that.
The 'search localdomain' doesn't look right to me.
That is probably there just because it is Red Hat's default
"private" domain. For example, Red Hat uses "localhost.localdomain"
in /etc/hosts for 127.0.0.1. They do this mainly so software which
gets confused without an FQDN has something to work with. I'm
guessing this isn't the problem. If DNS is working right, it
shouldn't take long for a lookup of "foo.localdomain." to return
NXDOMAIN (non-existant domain) anyway.
-- Ben
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
