Am Sat, 21 Aug 2010 09:15:26 +0059 schrieb Jorge Almeida <jjalme...@gmail.com>:
[...]
> I don't know about dhcpcd, but I'm using dhclient, and it works like this:
> $cat /etc/resolv.conf
> config_eth0=("dhcp")
> modules_eth0=("dhclient")
> dhcp_eth0="nodns"
>
> I'm not sure the last line is necessary.
> Then:
>
> $ cat /etc/dhcp/dhclient.conf
> append option domain-name-servers 127.0.0.1
>
> Substitute 127.0.0.1 by 8.8.8.8
With dhcpcd you can do something similar. When I was setting up dnsmasq on my
system I found out you can create hooks for dhcpcd; for instance,
in /etc/dhcpcd.enter-hook I have (well, now "had"):
# Prepend localhost to the list of DNS servers
new_domain_name_servers="127.0.0.1 ${new_domain_name_servers}"
The resulting resolv.conf:
marcec marcec # cat /etc/resolv.conf
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
search huntemann.uni-oldenburg.de
nameserver 127.0.0.1
nameserver 192.168.0.250
# /etc/resolv.conf.tail can replace this line
However, the comments in resolv.conf indicate you you can create one or both of
/etc/resolv.conf.{head,tail}, which will be merged into /etc/resolv.conf
automatically! The resulting resolv.conf:
marcec marcec # cat /etc/resolv.conf
# Generated by dhcpcd from eth0
# force localhost as first nameserver
nameserver 127.0.0.1
search huntemann.uni-oldenburg.de
nameserver 192.168.0.250
# /etc/resolv.conf.tail can replace this line
So both methods are slighly different. I think I'll stick with the latter now,
as I think it's more correct. However, I'm not sure whether this works with
other DHCP clients or just for dhcpcd.
> HTH
>
> Jorge
HTH
--
Marc Joliet
--
Lt. Frank Drebin: "It's true what they say: cops and women don't mix. Like
eating a spoonful of Drāno; sure, it'll clean you out, but it'll leave you
hollow inside."
signature.asc
Description: PGP signature
