dhcpcd - dns only

Hi!

I have configured my local network using fix local ip addresses and dns
server ips provided by my ISP.

Unfortunately those dns ips do not work as expected most of the times.
Everybody seems to use dhcp.

Is it possible to use dhcpcd (any other linux dhc client?) for dns ips
only keeping local ip addresses fixed?

Thanks.

On 2010-12-08 21:37:57 -0500, Paulo da Silva said:

> Hi!
>
> I have configured my local network using fix local ip addresses and dns
> server ips provided by my ISP.
>
> Unfortunately those dns ips do not work as expected most of the times.
> Everybody seems to use dhcp.
>
> Is it possible to use dhcpcd (any other linux dhc client?) for dns ips
> only keeping local ip addresses fixed?
>
> Thanks.

There are probably a couple of different ways to handle this. At first
glance, you could configure DHCPd with reservations for each of your
systems, so that the systems always get the same IP address. This
allows you the freedom to change the other parameters (such as DNS
servers) without having to reconfigure all the systems, but still
ensures the systems always have the same IP address.

Alternately (and I haven't confirmed this), you might be able to
configure the DHCP client (via dhclient.conf, IIRC) to only obtain
certain pieces of information from the DHCP server. However, I tend to
think that this approach won't work for you. Of course, I could be
wrong (wouldn't be the first time).

Hope this helps!

--
Scott
http://blog.scottlowe.org

Em 09-12-2010 03:15, Scott Lowe escreveu:
> On 2010-12-08 21:37:57 -0500, Paulo da Silva said:
>
>> Hi!
>>
>> I have configured my local network using fix local ip addresses and dns
>> server ips provided by my ISP.
>>
>> Unfortunately those dns ips do not work as expected most of the times.
>> Everybody seems to use dhcp.
>>
>> Is it possible to use dhcpcd (any other linux dhc client?) for dns ips
>> only keeping local ip addresses fixed?
>>
>> Thanks.
>
> There are probably a couple of different ways to handle this. At first
> glance, you could configure DHCPd with reservations for each of your
> systems, so that the systems always get the same IP address. This allows
> you the freedom to change the other parameters (such as DNS servers)
> without having to reconfigure all the systems, but still ensures the
> systems always have the same IP address.
>

OK. I used the dhcpcd -r <pretended ip address> and it worked.

I had tried that before but I was requesting an address out of the pool
of addresses reserved for dhcp on my router and it failed.

So I just need to reconfigure the router for a new range of dhcp
addresses and then use -r <ip> for each computer.

Thank you very much.
Paulo

On Thu, 09 Dec 2010 02:37:57 +0000, Paulo da Silva wrote:
>
> I have configured my local network using fix local ip addresses
> and dns server ips provided by my ISP.
>
> Unfortunately those dns ips do not work as expected most of
> the times. Everybody seems to use dhcp.

You are not restricted to using _just_ your ISP's dns servers.
You can set 3 (or more?) _diverse_ dns servers in /etc/resolv.conf
I purposely do _not_ use my ISP's dns servers, and I use one
dns server from each of three diffrent internet 'biggies'.

Example:
|$ cat /etc/resolv.conf
|domain ......
|
|# From `namebench` 14-Sep-10:
|nameserver 128.xxx.xxx.xxx
|nameserver 68.xxx.xx.xxx
|nameserver 205.xxx.xx.x


Recommended: `namebench` -- download and run to locate the closest,
fastest dns servers/resolvers near you.

http://code.google.com/p/namebench/

HTH,
Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
38.24N 104.55W | @ config.com | Jonesy | OS/2
* Killfiling google & XXXXbanter.com: jonz.net/ng.htm

In message <(E-Mail Removed) om>,
Allodoxaphobia wrote:

> You are not restricted to using _just_ your ISP's dns servers.
> You can set 3 (or more?) _diverse_ dns servers in /etc/resolv.conf
> I purposely do _not_ use my ISP's dns servers, and I use one
> dns server from each of three diffrent internet 'biggies'.

Only my router machine is set to use external DNS servers. The others go via
the router machine, which runs dnsmasq.