Am 15.06.2011 20:53, schrieb Dale:
> Juan Diego Tascón wrote:
>> On Wed, Jun 15, 2011 at 9:27 AM, YoYo Siska<yoyo@gl.ksp.sk>  wrote:
>>   
>>> On Wed, Jun 15, 2011 at 04:07:43PM +0200, Florian Philipp wrote:
>>>     
>>>> Hello list!
>>>>
>>>> for some wireless access points, I want to get an IP via DHCP but not
>>>> use the provided DNS-server (I use an openvpn setup with its own DNS
>>>> server, domain name, etc.).
>>>>
>>>> In /usr/share/doc/openrc-0.8.2-r1/net.example it reads:
>>>> # Setting name/domain server causes /etc/resolv.conf to be overwritten
>>>> # Note that if DHCP is used, and you want this to take precedence then
>>>> # please put -R in your dhcpcd options
>>>>
>>>> But dhcpcd does not seem to have a -R option. It does have a --static
>>>> option, though. While this is good enough for simply setting the DNS
>>>> server, it does not seem to allow specifying domain names or
>>>> search-domains (at least it is not shown in the man-page).
>>>>
>>>> Please tell me what the proper way is and whether the mention of
>>>> "-R" is
>>>> a documentation bug.
>>>>
[...]
>>>
>>>              So to stop dhcpcd from touching your DNS or MTU settings
>>> you would do:-
>>>                    dhcpcd -C resolv.conf -C mtu eth0
>>>
[...]
>>
>> I use the google dns servers so I created a /etc/resolv.conf file and
>> set the i attribute on it:
>>
>> chattr +i /etc/resolv.conf
>>
>> that way it can't be removed or overwritten and you won't have that
>> problem no matter what dhcp client you are using
>>
[...]
> dhcp_eth0="nodns"

A, great. That's exactly what I was looking for. Wonder why I overlooked
it. Probably because I searched the example file for DNS and dns. -.-

Thanks for all the proposals! I guess I stick with the nodns option. The
others aren't bad to know, either.

Regards,
Florian Philipp