Its a real shame for this issue to not have a solution implemented even after 8+ years of raising the issue.
Today I did a fresh installation of Ubuntu 15.10 on my HP laptop, and after installation opened firefox and found that it was taking extremely long time for even the google page to come up. It has nothing to do with my internet connection as I have a good fast internet connection. I was not even able to search for a solution. I have experienced this before and many friends for whom I installed Ubuntu and derivatives like elementary used to share the similar bad experience. Is it possible to get this fix implemented with ubuntu default installation? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/94940 Title: mdns listed in nsswitch.conf causes excessive time for dns lookups Status in avahi package in Ubuntu: Confirmed Status in nss-mdns package in Ubuntu: Confirmed Status in nss-mdns package in Debian: Fix Released Bug description: Binary package hint: avahi-daemon I encountered this problem on a machine that is integrated into our work network. I performed a dist-upgrade to Feisty on my desktop and all went well. I've noticed recently that any dns based work seemed to take a significantly longer time then normal. My system is getting dns information on our company internal systems from two dns servers. Previously, if I tried to establish an ssh connection with another system I could generally expect the connection in under 3 secs. After the dist-upgrade the time went from under 3 seconds to approximately 25 seconds. After searching around the system I found an entry in /etc/nsswitch.conf that cause me a little concern. The line in question is: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I looked around a bit and it seems that the references to mdns are really talking about communication with the Avahi mDNS/DNS-SD daemon. Since this looks to be a part of a zeroconf configuration I wasn't expecting too much in my current environment, as we really only have three Mac's. What concerned me is the idea that if we hit files with no answer there is a delay while we hit the other options until we hit dns, which is where the information I seek existed. For an experiment I tried two separate tests. The first changed the line to looks like: hosts: files dns mdns4_minimal [NOTFOUND=return] mdns The change should have improved the time, but I was still looking at approximately 23 seconds to return a command prompt on the destination machine. Finally, I change the entry to simply: hosts: files dns After this change I was again receiving the destination command prompt in under 3 seconds. I don't know if simply changing the file will correct the problem long-term or not. Seems to help me, but might be the way to go for most Ubuntu users. ProblemType: Bug Architecture: i386 Date: Thu Mar 22 18:10:54 2007 DistroRelease: Ubuntu 7.04 Uname: Linux samdesk 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/94940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
