Bug#555660: No DNS name resolution after upgrade from 2.9-25 to 2.10.1-5

2009-11-11 Thread Aurelien Jarno
forcemerge 552010 555660 thanks On Wed, Nov 11, 2009 at 09:42:54PM +0100, Thomas Viehweger wrote: > > > What is the content of your /etc/resolv.conf? > > > > It is almost empty, I have not touched the file: > > > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > > resolvconf

Bug#555660: No DNS name resolution after upgrade from 2.9-25 to 2.10.1-5

2009-11-11 Thread Thomas Viehweger
> > What is the content of your /etc/resolv.conf? > > It is almost empty, I have not touched the file: > > # 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 Thanks for the hint. I now added

Bug#555660: No DNS name resolution after upgrade from 2.9-25 to 2.10.1-5

2009-11-11 Thread Thomas Viehweger
>> My current workaround is to make a manual nslookup which works and writing >> the result to /etc/hosts. > What is the content of your /etc/resolv.conf? It is almost empty, I have not touched the file: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT

Bug#555660: No DNS name resolution after upgrade from 2.9-25 to 2.10.1-5

2009-11-10 Thread Aurelien Jarno
On Tue, Nov 10, 2009 at 10:41:45PM +0100, Thomas Viehweger wrote: > Package: libc6 > Version: 2.10.1-5 > Severity: major > > Name resolution stops working for me mostly after upgrading testing > distribution. > > Example: > > ping heise.de > ping: unknown host heise.de > > > nslookup heise.de >

Bug#555660: No DNS name resolution after upgrade from 2.9-25 to 2.10.1-5

2009-11-10 Thread Thomas Viehweger
Package: libc6 Version: 2.10.1-5 Severity: major Name resolution stops working for me mostly after upgrading testing distribution. Example: > ping heise.de ping: unknown host heise.de > nslookup heise.de Server: 127.0.0.1 Address:127.0.0.1#53 Non-authoritative answer: Name: h