No DNS at computer start

[_kai_]

Hi

I have a problem when start my computer: The DNS ip servers are gone!

I have to put it again and again in every reboot.

I open the "Systems Preferences -> Red Parameters -> DNS" and write out my DNS IPs, then when I restarted my computer, they are lost.

Greetings!

[Pierre Buard (pierre-buard)]

Check if this package is installed : resolvconf.
It was present on a computer which had Xubuntu breezy and then was updated to dapper.
After removal, /etc/resolv.conf isn't overwritten anymore (which is were your DNS are stored).

[_kai_ (gpayo)]

I do have the resolvconf package, but I didn't update
my current kubuntu installation from any *ubuntu: My
installation was from an empty disk.

So, Do I have remove the resolvconf package?

Thanks!

 --- Pierre Buard <email address hidden> escribió:

> Check if this package is installed : resolvconf.
> It was present on a computer which had Xubuntu
> breezy and then was updated to dapper.
> After removal, /etc/resolv.conf isn't overwritten
> anymore (which is were your DNS are stored).
>
> --
> No DNS at computer start
> https://launchpad.net/bugs/54115
>

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/

[Pierre Buard (pierre-buard)]

I am sorry but all I can say is that on a DSL connection, behind a router, with fixed IPs and DNS servers : my computers don't need this software (Xubuntu had it, but Kubuntu didn't).

The description says that if you are using DHCP (be it dialup or a direct connection), you need this package for DNS resolution.

You can test whether this package is essential without removing it. You simply need to prevent the execution of the service :
sudo chmod -x /etc/init.d/resolvconf

If after reboot you lost your connection then restore it :
sudo chmod +x /etc/init.d/resolvconf

In case it doesn't work, try disabling the program itself :
sudo chmod -x /sbin/resolvconf

My knowledge in this is essentially empirical so : it should work (tm)

[_kai_ (gpayo)]

Alright, I got you way of thinking (or the way you
think I can solve my problem), but resolvconf does not
seems to be the problem, because it are not running on
the current runlevel (2).

But thanks!

 --- Pierre Buard <email address hidden> escribió:

> I am sorry but all I can say is that on a DSL
> connection, behind a
> router, with fixed IPs and DNS servers : my
> computers don't need this
> software (Xubuntu had it, but Kubuntu didn't).
>
> The description says that if you are using DHCP (be
> it dialup or a
> direct connection), you need this package for DNS
> resolution.
>
> You can test whether this package is essential
> without removing it. You simply need to prevent the
> execution of the service :
> sudo chmod -x /etc/init.d/resolvconf
>
> If after reboot you lost your connection then
> restore it :
> sudo chmod +x /etc/init.d/resolvconf
>
> In case it doesn't work, try disabling the program
> itself :
> sudo chmod -x /sbin/resolvconf
>
> My knowledge in this is essentially empirical so :
> it should work (tm)
>
> --
> No DNS at computer start
> https://launchpad.net/bugs/54115
>

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/

[Pierre Buard (pierre-buard)]

It is simply a service to update DNS. There is no need for it to run in the background. Therefore it's launched on bootup in runlevel S. But just to be sure, I installed it on one of my computer and guess what, no more DNS ! I don't know about you but since it doesn't do me any good I prefer to remove it rather than learn how to operate it (at least for now).

Here is short explanation from <http://ubuntuforums.org/showthread.php?t=89491> :
runlevel S: the first runlevel in boot process. /etc/init.d/rcS script will be invoked to start and all the processes underneath /etc/rcS.d will be executed.
runlevel 1: the single user mode. All processes underneath /etc/rc1.d will be executed.
runlevel 2,3,4,5: in debain system, the multi-user env, may not may not include GUI. The same, processes under each of the corresponding dirs will be run.
runlevel 0: computer shutdown.
runlevel 6: computer reboot.

[_kai_ (gpayo)]

It works!

I just remove the resolvconf package and it works!

Thank you man!

 --- Pierre Buard <email address hidden> escribió:

> It is simply a service to update DNS. There is no
> need for it to run in
> the background. Therefore it's launched on bootup in
> runlevel S. But
> just to be sure, I installed it on one of my
> computer and guess what, no
> more DNS ! I don't know about you but since it
> doesn't do me any good I
> prefer to remove it rather than learn how to operate
> it (at least for
> now).
>
> Here is short explanation from
> <http://ubuntuforums.org/showthread.php?t=89491> :
> runlevel S: the first runlevel in boot process.
> /etc/init.d/rcS script will be invoked to start and
> all the processes underneath /etc/rcS.d will be
> executed.
> runlevel 1: the single user mode. All processes
> underneath /etc/rc1.d will be executed.
> runlevel 2,3,4,5: in debain system, the multi-user
> env, may not may not include GUI. The same,
> processes under each of the corresponding dirs will
> be run.
> runlevel 0: computer shutdown.
> runlevel 6: computer reboot.
>
> --
> No DNS at computer start
> https://launchpad.net/bugs/54115
>

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.espanol.yahoo.com/

[Marcos Dione (mdione)]

I found what seems to be a bug in resolvconf. to specify static dns servers for a netiface, you can add the following to /etc/network/interfaces:

iface eth1 inet static
    name faraway
    address 200.69.231.1
    netmask 255.255.255.252
    broadcast 200.69.231.3
    gateway 200.69.231.2
    dns-nameserver 200.69.193.111 200.69.193.112 # this one

resolvconf is executed via /etc/network/if-up.d/000resolvconf when the netiface is brought up, with some environment variables set up. within those envvars there is IF_DNS_NAMESERVER, which has the value of the dns-nameserver field there above. the problem is that /etc/network/if-up.d/000resolvconf is checking for IF_DNS_NAMESERVERS, with a trailing S, so it thinks there are no nameservers and acts accordingly.

I'm not sure if the bug is in resolvconf or in ifupdown, though.