On Sat, Nov 14, 2009 at 11:10, Aurelien Jarno
<aurelien@aurel32.net> wrote:
Either add a nameserver entry to /etc/resolv.conf, or upgrade to version
2.10.1-7 where this problem is fixed.
This works. Actually, I added 'nameserver 127.0.0.1' to /etc/resolvconf/resolv.conf.d/base and ran 'resolvconf -d'.
This means that my problem actually belongs to bug #552010. It is regrettable that this nasty known problem is propagated to testing without warning. If I would have had only one computer, I would have been forced to go to the competition to be able to report the problem. :-)
Thanks for your quick reply.
Simon Pepping