Any news on this? Did you report this bug upstream?
Here is a sample session showing the effect: # ping lxc01 PING lxc01.example.de (172.16.99.198) 56(84) bytes of data. From dpcl082.example.de (172.16.97.128) icmp_seq=1 Destination Host Unreachable From dpcl082.example.de (172.16.97.128) icmp_seq=2 Destination Host Unreachable From dpcl082.example.de (172.16.97.128) icmp_seq=3 Destination Host Unreachable ^C --- lxc01.example.de ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3050ms pipe 4 # service nscd stop # ping lxc01 PING lxc01.example.de (172.16.99.28) 56(84) bytes of data. 64 bytes from lxc01.example.de (172.16.99.28): icmp_seq=1 ttl=64 time=0.362 ms 64 bytes from lxc01.example.de (172.16.99.28): icmp_seq=2 ttl=64 time=0.396 ms ^C --- lxc01.example.de ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.362/0.379/0.396/0.017 ms # service nscd start # ping lxc01 PING lxc01.example.de (172.16.99.198) 56(84) bytes of data. From dpcl082.example.de (172.16.97.128) icmp_seq=1 Destination Host Unreachable From dpcl082.example.de (172.16.97.128) icmp_seq=2 Destination Host Unreachable From dpcl082.example.de (172.16.97.128) icmp_seq=3 Destination Host Unreachable ^C --- lxc01.example.de ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3050ms pipe 4 See how the old IP address pops up again, as soon as nscd is active? Obviously "service nscd stop" did not flush the cache. Regards Harri -- aixigo AG, Karl-Friedrich-Strasse 68, 52072 Aachen, Germany phone: +49 241 559709-79, fax: +49 241 559709-99 eMail: harald.dun...@aixigo.de, web: http://www.aixigo.de Amtsgericht Aachen - HRB 8057, Vorstand: Erich Borsch, Christian Friedrich, Tobias Haustein, Vors. des Aufsichtsrates: Prof. Dr. Ruediger von Nitzsch