On 8/27/06, linux23dragon <[EMAIL PROTECTED]> wrote:
On Sunday 27 August 2006 02:07, linux23dragon wrote:
> -------------------------
>
> "/etc/resolv.conf"
>
> # no entry placed in this file #
>
> -------------------------
>
Well it worked, after I knew the DNS address of the router. Then I just
needed to include the DNS settings to the "/etc/resolv.conf" file :)
The problem with editing resolv.conf is that the DHCP client is going
to overwrite it every time. The proper solution shouldn't require any
extra configuration unless it can't find the DHCP server on the
router. AFAIK, dhcp should find that server automatically and fill out
resolv.conf with the proper values.
If it doesn't find it, then the proper way to handle this is to add
the IP address to /etc/dhclient.conf. You'd want to add another
prepend line with that IP address. It should stop looking for servers
when it finds the first one. The reason 127.0.0.1 is there is in the
event where you're using a caching name server.
interface "eth0"{
prepend domain-name-servers 127.0.0.1;
prepend domain-name-servers w.x.y.z;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, host-name;
require subnet-mask, domain-name-servers;
}
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
