[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Only precise is still supported and affected by this bug, I don't think this is worth the effort fixing it -- 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: Fix Released Status in nss-mdns package in Ubuntu: Fix Released 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
** Changed in: avahi (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nss-mdns (Ubuntu) Importance: Medium => High ** Changed in: nss-mdns (Ubuntu) Status: Confirmed => Fix Released -- 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: Fix Released Status in nss-mdns package in Ubuntu: Fix Released 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
I would think that could potentially open you up to something bad. Say you have payroll.mydomain.local and I join my linux box 'named 'payroll'. Now someone goes to http://payroll.mydomain.local/ and it hits my box. Switching MDNS to the end (files dns mdns4_minimal [NOTFOUND=return]) should fix the issue in cases where DNS wasn't down for some reason. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
>From https://en.m.wikipedia.org/wiki/.local#Multicast_DNS_standard "Implementers MAY choose to look up such names concurrently via other mechanisms (e.g., Unicast DNS) and coalesce the results in some fashion. Implementers choosing to do this should be aware of the potential for user confusion when a given name can produce different results depending on external network conditions (such as, but not limited to, which name lookup mechanism responds faster)." So wouldn't that solve the issue? -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
This thing is a real problem and there must be a solution for that. every new Ubuntu computer I set up in our wrongly configured Windows network has connection problems. There is this msdn article which recommended setting up the network so lots of people are doing that. Can't there be some connection check after the installation which makes the user aware of the problem and tell him to fix his Network or go to compatibility mode where printers might not work ? this is something I would expect from user-friendly distribution with Ubuntu definitely is. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
By all means, go ahead and switch Kristian, although I ran into the same issue on a few Debian boxes I installed recently. I'd rather have mdns and avahi enabled by default because a lot of printers rely on them. I also don't want to have to answer additional questions during the install. Like many people have said above, the problem is due to a misconfiguration on your network. Don't use '.local' for your Windows domain. If you can't change your internal domain, there's an easy work- around that's documented above as well. Why should we break a commonly-used protocol because *your* network is mis-configured? Please stop whining about it and threatening to switch because it's not productive and doesn't have any bearing on solving the issue. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
This is a longstanding and huge issue meaning that everyone should just switch back to Debian instead of using Ubuntu if no one is going to fix this bug. It is worse now. All mdns, avahi, etc should be removed from Ubuntu by default and made an OPTIONAL config choice during or after 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
FYI - Microsoft KB296250 is the article where they recommend using '.local'. It was last updated in 2007. https://support.microsoft.com /en-us/kb/296250 RFC6762 describes the use of mDNS and the .local TLD. https://tools.ietf.org/html/rfc6762 While RFC6762 came after Microsoft's KB article, RFCs describe industry standards and best practices. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Hi, I had this issue in Ubuntu 15.10 fresh install. I know my PTR is oke. host: cc04 localdomein: bla.example ping cc04 works, gives me the IP and the reverse lookup ping cc04.bla.example does not work. after removing mdns4_minimal [NOTFOUND=return] from /etc/nsswitch everything is working again. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Aaron C. de Bruyn wrote: > With all due respect +thejranjan, it's not really Ubuntu's fault. > Microsoft recommended for years that companies use '.local' as their > internal domain suffix so as not to conflict with the existing DNS > namespace like .com, .net, .org, etc... The issue of slow *reverse* lookups for IP addresses lacking a PTR record in the DNS has nothing to do with Microsoft or .local. I still don't see the point of doing mdns resolution of reverse lookups at all. -- Andreas Gustafsson, g...@gson.org -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Thank you for a detailed and competent answer. This clarifies the issue. Now it makes sense why this cannot and should not be fixed in Ubuntu. To summarize: If you experience lookup delays, change your /etc/nsswitch.conf to this: $ cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat # https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/94940 # Original, delayed lookup on improperly configured internal networks: #hosts: files mdns4_minimal [NOTFOUND=return] dns # Use this if you're not on a local network with Microsoft services or if you don't need on them: #hosts: files dns # Delays looking up hosts on your internal network, but you *will* get the best of both worlds; # multicast DNS resolution *and* resolution of your incorrectly-named internal network: hosts: files mdns4_minimal dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
With all due respect +thejranjan, it's not really Ubuntu's fault. Microsoft recommended for years that companies use '.local' as their internal domain suffix so as not to conflict with the existing DNS namespace like .com, .net, .org, etc... Unfortunately Microsoft just decided to recommend .local without thinking it through or registering .local with any standards body. Later on a standards body decided to use .local for Multicast DNS. So you run into this problem when you connect your Ubuntu box (and I believe Debian as well) to a Microsoft Windows network that *violates* established standards. The fix is easy enough--edit /etc/nsswitch.conf and remove multicast DNS. That gives you access to your internal network which is configured improperly. Unfortunately you might have trouble communicating with multicast DNS services. A work-around is to remove the '[NOTFOUND=return]' part of the mdns config. That basically tells the system to try looking up from multicast DNS and immediately fail if multicast DNS doesn't find anything. If you remove it, you will still have delays looking up hosts on your internal network, but you *will* get the best of both worlds-- multicast DNS resolution *and* resolution of your incorrectly-named internal network. So there's nothing really for Ubuntu to fix. It's up to you to fix your internal network or make a change to your Ubuntu install so it can communicate with your improperly configured internal network. -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Still present in 14.04 trusty on Desktop (not Server), see http://www.claudiokuenzler.com/blog/600/ubuntu-desktop-ntp-ntpdate- error-resolving-name-or-service-not-known-mdns -- 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
[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
** Tags added: feisty i386 karmic lucid maverick precise raring saucy -- 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