Comment 0 for bug 994227

While resolvconf daemon is running, I cannot use the network, because my resolv.conf file is filled with invalid nameservers soon after connection:

========================== bash session: ==========================
# service resolvconf status
resolvconf start/running
# file /etc/resolv.conf
/etc/resolv.conf: symbolic link to `../run/resolvconf/resolv.conf'
# export LC_ALL=C; service resolvconf status; date; dhclient wlan0 ; cat /etc/resolv.conf; date; inotifywait /etc/resolv.conf; date; cat /etc/resolv.conf
resolvconf start/running
Fri May 4 00:50:48 MSK 2012
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd reload

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.129.129
nameserver 8.8.8.8
nameserver 94.25.128.74
Fri May 4 00:50:50 MSK 2012
Setting up watches.
Watches established.
/etc/resolv.conf OPEN
Fri May 4 00:52:44 MSK 2012
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 94.25.128.74
nameserver 94.25.208.74

==============================================================================

To clarify servers:
192.168.129.129 is my ISP DNS
8.8.8.8 backup server configured in my router
94.25.128.74… what's that?

# egrep -nR '94.25.(12|20)8.74' /etc/*
/etc/resolv.conf:3:nameserver 94.25.128.74
/etc/resolv.conf:4:nameserver 94.25.208.74

So these last two servers cannot be found in the configs, but somehow appear in resolv.conf. They are not delivered by dhclient either. I guess they may be root DNSes for my ISP (according to whois info), but I'm unable to surf the Internet with their help.

The delay until resolv.conf gets corrupted is not constant at all, sometimes it's as small as 3 seconds. one time is was 13 seconds.
If I reconnect and shut down resolvconf, I get a working network without any problems. This behavior seems to be a regression after apt-get upgrade from ubuntu 11.10 and seems to be a blocker to an ordinary user, since the network is effectively unusable.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: resolvconf 1.63ubuntu12
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 3 23:57:11 2012
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)