At a client site using a few Windows 2003 Servers, I would connect to an Ubuntu vmware image that had DNS of lamp.custname.local regularly with Gutsy beta.
During the beta I was out here quite a bit, but about a week before Gutsy launched until today I hadn't been out here. Now when I plug my laptop into the network and try to ssh or ping lamp.custname.local I get nothing. If I do an nslookup it returns the correct IP from the DNS server. Doing a bit of stracing and debugging led me to nsswitch.conf and this bug. I changed nsswitch.conf like so: [EMAIL PROTECTED]:/etc$ diff nsswitch.conf nsswitch.conf.old 11c11 < hosts: files dns mdns4 --- > hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve stuff correctly out of DNS, but I can't resolve avahi stuff--which I think is to be expected removing mdns4_minimal--but then what is the mdns4 line for? -- mdns listed in nsswitch.conf causes excessive time for dns lookups https://bugs.launchpad.net/bugs/94940 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
