Carl Thorn wrote:
> Carl Thorn wrote:
>
>> It is definitely a nameserver thing. I have dhcpcd installed and it
>> generates /etc/resolv.conf automatically but lists my dsl modem as the
>> nameserver. When I manually entered the nameservers of my isp everything
>> worked. So now I have to figure out how to reconfigure the hooks so I
>> don't have to manually change the /etc/resolv.conf on every reboot.
>
> man dhcpcd
> Thanks I will take your word for it but the above line doesn't seem
> to exist in my version of man dhcpcd
I don't use dhcp myself. I prefer static addresses to avoid problems
like yours. My response was probably from an old version on the
internet. The most recent version is dhcpcd-5.2.2.tar.bz2.
I downloaded that and found:
-C, --nohook script
Don't run this hook script. Matches full name, or prefixed
with 2 numbers optionally ending with .sh.
So to stop dhcpcd from touching your DNS or MTU settings
you would do:-
dhcpcd -C resolv.conf -C mtu eth0
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
