DNS resetting after each reboot - Debian Lenny

[imranka]

Hi,

Most of the time I rebooting, my resolv.conf is getting updated by resolvconf program, so the network connection cannot be reached.

I followed this :

Debian User Forums • View topic - Solving DNS problem (dhclient & resolv.conf)

but the problem still persist.

Can any body help?

[Segfault]

IMO man pages are much better source of information than somebody's hack

dhclient(8) - Linux man page
dhclient.conf(5): DHCP client config file - Linux man page

That said, I do not use DHCP with desktop computers. Static configuration is better, you can access computers by IP addresses and one less program is running.

[imranka]

Hi Segfault,

Thanks for your reply.

I have also manually configured my network without dhcp, but don't know how this dhcp service is running at boot time and resetting the resolv.conf file. I followed your second link, and saw,

 do-forward-updates  false

will stop the dhcp service from updating the dns, if I am not wrong. But still the same problem is occurring.

Can you kindly elaborate on:

1. How I can stop the dhcp service from running

or

2. Even if it runs, how I can stop it from interfaring with the dns setting

option 2 will be better for me

[Segfault]

sudo vi /etc/network/interfaces

You will see something like

iface eth0 inet dhcp

replace it with static configuration, using 192.168.1.10 as an example

iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254

I'm sure all this information can be seen with man interfaces in your Debian box.

[Segfault]

Debian has excellent documentation, when I was running Debian I never felt the need to ask for help, everything is just here!

[imranka]

Thanks once again. My /etc/network/interface file shows:

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
	address 192.168.1.2
	netmask 255.255.255.0
	network 192.168.1.0
	broadcast 192.168.1.255
	gateway 192.168.1.1
	# dns-* options are implemented by the resolvconf package, if installed
	dns-nameservers 192.168.1.1

And I see, not everytime the resolv.conf is getting reset, but it is happening sometime.

[jdkaye]

Hi Imranka,
I had a similar problem which was that my ISP imposed its own dns server on me which I don't like. I am using dhclient (version 3) and it's conf file is in /etc/dhcp3/dhclient.conf
I am using a wlan0 (wireless) interface and so I put this in my dhclient.conf file

interface "wlan0" {
    prepend domain-name-servers 169.237.32.1,64.127.100.11;
}

The "prepend domain-name-servers" command insures that I use the domain name servers that I want and not the ones the ISP tries to impose. You can adapt this solution to your Debian version which may be running an earlier version of dhclient. In that case the conf file would be in /etc/dhcp instead of /etc/dhcp3
Cheers,
jdk

[rcgreen]

The generation of the resolv.conf file (actually stored at
/var/run/resolvconf/resolv.conf , to which /etc/resolv.conf is
to be symlinked) can be controlled by the admin by editing
/etc/resolvconf/update.d/libc . Different strategies can be
implemented: e.g., one possible strategy would be to put only the most
recently provided information into resolv.conf . The current default
strategy is to put *all* available resolver information into
resolv.conf, ordered by interface type as follows: lo, eth*, ppp* .
This strategy will need to be refined, I know, but it works for me
in its current form.

The admin can of course disable resolv.conf automagic by deleting the
/etc/resolv.conf symlink and putting a static file at that location.

Resolvconf -- a package to manage /etc/resolv.conf