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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
mdns listed in nsswitch.conf cau
** 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
Bugs, which is
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
>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
confusio
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 connect
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 m
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...
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 *reve
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 configu
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
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
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.
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 agai
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
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Tags added: feisty i386 karmic lucid maverick precise raring saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
mdns listed in nsswitch.conf causes excessive time for dns lookups
I confirm that this bug is still present in 13.10 (clean install).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
mdns listed in nsswitch.conf causes excessive time for dns lookups
To
Still a problem in 13.10 as far as I can tell. Fix #75 helped.
According to this log, a fix was released nearly a year ago, but still
people keep finding the bug. How does this Launchpad work again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I can confirm that this is still a problem on 13.04. I have noticed it
affecting:
ping
ssh
ntp
I fix by using the following line in /etc/nsswitch.conf:
hosts: files dns
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Has the fix been applied to 12.04 and 13.04? I am getting abnormal
network activity. Many small packets are send/received and is do to
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
** Changed in: nss-mdns (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
mdns listed in nsswitch.conf causes excessive time for dns lookups
To
For me this change (minimal change, only adding "[NOTFOUND=return]" after dns,
not changing the order) in /etc/nsswitch.conf fixed my problem of slow SSH
connecting in internal network (where UseDNS=no in sshd_config did not help):
-hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
Great. I just spent half a day debugging my network (as I've just set
up my own bind service on a new server) before I finally found an
article[1] and later this bug report that explained what was going on
and how to fix it.
I noticed that my Ubuntu Server has the working nsswitch.conf installed
Many people would have "cheap home routers", so this still is very
annoying. It spreads delays over a wide range of applications while not
showing an explanation or progress indicator to the "normal user".
What are the caveats of changing the nsswitch.conf like stated above?
--
You received this
A default installation of Microsoft Small Business Server Essentials
2011 will use a .local domain. It is quite tedious to override this
choice (http://titlerequired.com/2011/08/02/installing-sbs-essentials-
using-an-answer-file/). Anyone using Ubuntu on such a network has to
remove the default mDN
On Precise 12.04 the reverse lookup causes ssh with gssapi enabled to wait for
~15-20 seconds before login.
Removing mdns4 from the hosts: line in /etc/nsswith.conf fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
This problem seems to have started for me at the time of upgrade from
11.04 to 11.10. Changing the resolve order in resolv.conf to:
files dns mdns4_minimal [NOTFOUND=return] mdns4 wins
fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
If anyone is interested, here's a related issue: bug# 788274
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/788274
I recently attached some tcpdumps with the report.
The experience is different from that of the original reporter. tweaking
in either /etc/nsswitch.conf or /etc/resolv.con
Can confirm this affects me on Oneiric Beta 2. Host has working IPv4
and IPv6 network. All networks have working reverse DNS, but not all
hosts have actual DNS entries (this is true of both IPv4 and IPv6).
Fix for me is to remove mdns4 from the nsswitch.conf.
"sudo /sbin/arp" takes a long time
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nss-mdns (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94940
Title:
mdn
Thanks for the tip, Dave. I've seen the single-request workaround before, it
did not seem to help. Maybe adding the string before the dns list works
better???
In my case the problem was with a few browsers at time being very sluggish,
namely, firefox, chromium and epiphany for some sites. A
My network was showing this (multiple) 5-second timeout problem. To test it, I
turned off DNS caching
# /etc/init.d/nscd stop
and then
# time curl -I www.google.co.uk
which consistently took more than 5 seconds.
I tried several of the approaches described above, and eventually determined
that the
Using 10.04 (64bit desktop) I was having important delays when using
ssh. The login prompt was taking several seconds to appear.
I changed the line to:
hosts: files mdns4_minimal dns [NOTFOUND=return] mdns4
and now it's connecting in a fraction of a second. I don't know why it
works alt
I just did a fresh install of Ubuntu 10.10 (i386 desktop), and the bug
is still there. Specifically, logging in to the Ubuntu machine over a
LAN configured with 10.x.x.x addresses and a configured DNS server that
immediately returns an NXDOMAIN response for the reverse mappings of
those addresses,
Regarding Microsoft suggesting in their documentation to use .local as
the tld for an Active Directory domain, that's just an example, not
really a suggestion, as in "you might want to use a name such as
"mycompany.local". This was back before the major problems with the
.local TLD and Bonjour/Ren
Using Ubuntu 10.04.01 in an interesting situation...
Local network is connected to router with a VPN Gateway.
All work traffic goes through NetworkA via VPN over NetworkB.
All non work traffic flows through Network B directly to the internet
(including NetworkC traffic).
Network B has it's own wi
problem is still here also in lucid
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I stumbled upon this issue as well. I am using ubuntu in a local network
with a local dns server, which serves foo.local hostnames. When I did a
"host bar.foo.local" I got the correct response "Host bar.foo.local has
IP xx.xx.xx.xx"; however f.e. "ping bar.foo.local" gave an "unknown
host" response
@Andreas: It seems that I _did_ have DNS problems. Disabling ipv6
certainly improved my overall situation (firefox, apt-get), but the test
case was still running slowly. Then i tried switching to OpenDNS, which
made your test case run very fast. So I guess my problem was the DNS
relay in my D-Link
damaan - the behavior you report suggests that you are in fact having
DNS problems, but that they are unrelated to mdns and this bug. Perhaps
you have addresses in your /etc/resolv.conf that do not point to working
DNS servers.
--
mdns listed in nsswitch.conf causes excessive time for dns looku
I installed Lucid beta2 and I'm experiencing slow networking, possibly
related to DNS problems.
I ran Andreas test3.c program attached above, it returns in little over
ten seconds with the default nsswitch.conf setting. I expected an
improvement when using "hosts: files dns", but it still took ten
Disabling mdns only for reverse lookups outside the local subnet(s)
would not solve the problem. The test3.c example program uses a non-
local, reserved address because that's a convenient way to illustrate
that the problem is not caused by the local DNS configuration, but the
actual delays I'm ex
Andreas: I'd guess in most cases reverse lookup with mdns is only useful
for IP addresses inside the current subnet(s), so you might have a point
there (but that would probably have to go into another bug report).
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs
The problem *does* occur with non-broken DNS servers, too. I just tried
the test program "test3.c" attached to my comment from 2007-05-13 on a
system booted from a Lucid alpha3 live CD, and it still takes more than
five seconds to execute. The system was directly querying a BIND 9 DNS
server, and t
As said before, the problem occurs when you use mDNS combined with a
broken DNS server. If your DNS server is not broken, you will not have
any delays. (Unfortunately the DNS relays on several cheap home routers
are broken...)
Some ways to solve this:
* try to detect broken DNS servers & configu
Same configuration change worked for me with no apparent problems. Why
does Ubuntu need multicast dns at all? Which software is responsible for
the bug? From the above comments it appears that the problem is inherent
in how mdns works. Then it would be preferable not to have mdns at all
rather than
so, i had the same issue ... after some analyze, i decided to remove package
'libnss-mdns'.
after that file /etc/nsswitch.conf will be update automatically to
hosts: files dns
well, everything works perfect now.
using karmic.
--
mdns listed in nsswitch.conf causes excessive time f
Has there been any progress on this issue? I experience slow DNS lookup
times on *all* my machines with Ubuntu (including Lucid), but not on any
version of Windows.
I can confirm that changing the "hosts" line in /etc/nsswitch.conf from:
files mdns4_minimal [NOTFOUND=return] dns mdns4
to:
files md
I think I have found some of the problem. avahi-daemon gets into a
weird state when it sees advertisements for both IPv4 and IPv6 addresses
for the same service. You will notice that when you run avahi-resolve
just after ifdown/ifup, you will be given an IPv6 address. About 2-8
seconds later tha
I had very weird problem with MacBook Pro and Ubuntu 9.10. When DNS
resolving was in progress, everything else was frozen. For example, I do
'ping news.google.com' in one terminal, everything looks good, then I go
and do 'ping linux.org.ru', and while DNS lookup is in progress, ping in
the first te
For me, turning off avahi-daemon on the target server solved the problem
entirely.
Perhaps the other fixes have already been applied by some deb updates.
In /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
I don't have any settings on DNS in /etc/ssh/ssh_config
Has anyone else tried:
hosts: files mdns_minimal [NOTFOUND=return] dns mdns
works perfectly for me and also fixes broken ipv6 mdns behavior.
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchpad.net/bugs/94940
You received this bug notification b
Hi,
My local domain in named xxx.local. The ubuntu machines cannot resolve hosts.
My solution is to remove [NOTFOUND=return] from line.
--
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
Still present in Karmic.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
I've confirmed this in Jaunty on two separate systems, with slow ping
times on local LAN servers.
--
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 subsc
** Changed in: nss-mdns (Ubuntu)
Status: Incomplete => New
** Changed in: nss-mdns (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchpad.net/bugs/94940
You received this bug notification be
I've reproduced the slow ssh login problem on: Intrepid Minimal CD
Install + ssh
There's no apparent avahi/mdns installed or activated
In that configuration, "-o GSSAPIAuthentication=no" on the client
command line has no effect, nor does setting it in the server's
ssh_config file (though why that
This bug is documented in http://www.ietf.org/rfc/rfc4795.txt and warned
against in the manpage to resolv.conf.
** Changed in: avahi (Ubuntu)
Status: Invalid => Confirmed
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchpad.net/bugs/94940
You recei
all,
i am on gutsy both the following changes are not working for me. browser works
fine for half a minute then the look ups are back to there horrible
limit..taking as much as 30 seconds..
files mdns4 [NOTFOUND=return] dns
or
files dns
any other suggestions..i can try out..
--
mdns listed i
Ok, so I don't pretend to understand everything in this post. If you,
like me, simply want to avoid delays logging in with ssh, stop avahi.
For me, a simple "ssh server" took about 10 secs. Running with "ssh -o
GSSAPIAuthentication=no server" brought that delay down to nothing. If
that is also true
** Changed in: avahi (Ubuntu)
Status: New => Invalid
--
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-bug
After reading through related bugs, it looks like avahi / nss is trying
multicast dns before traditional dns. With multicast DNS, the only real
option is long timeouts and retries, since only one avahi-enabled
machine on the network may have a response for a given request. (That
is, a successful lo
> Is there a reason why requests that get NXDomain responses are
retried? I can't think of a situation where that would be what you'd
want, but maybe I'm missing something.
Speaking as a long-time participant in the standardization of the DNS
protocol, I can assure you that retrying a request that
After some stracing and tcpdumping, it looks like the changed behavior
here is that when mdns gets an NXDomain response, it retries up to 5
seconds, then reports a "timeout" to the requesting client, rather than
immediately reporting that the record doesn't exist.
Is there a reason why requests th
I'm torn.
As much as I despise Microsoft, I am forced (at work) to touch quite a few
Windows domains. This means I either have to disable avahi on my laptop and
remove mdns from nsswitch, or not be able to resolve computers on almost every
client network we support.
Even microsoft suggests in
Aaron: exactly, and yes, using another domain should fix your problem
--
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.
--
Thanks for the info Jan.
So in my case, the issue I am seeing may be due to the fact that avahi
thinks it is supposed to resolve .local addresses. If the internal
network were named something different, this issue would potentially go
away?
--
mdns listed in nsswitch.conf causes excessive time
Aaron, .local is the proposed reserved top-level domain (TLD) for link-
local addresses, to be queried by mDNS (multicast DNS) instead of
"normal" DNS. AFAIK currently this is a draft which is scheduled to
become an IETF RFC: http://files.multicastdns.org/draft-cheshire-dnsext-
multicastdns.txt
E
I should also mention I looked at the freedesktop.org link Martin posted and
that didn't resolve the issue.
And I should clarify that the domain I mentioned (custname.local) is not an
avahi configured domain, it is the name we assigned active directory, and the
only DNS server on the network is
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 lap
I was able to fix this in feisty by replacing mdns4_minimal with mdns4.
Before:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
After:
files mdns4 [NOTFOUND=return] dns
Works like a charm, and I can still resolves hosts using mdns.
--
mdns listed in nsswitch.conf causes excess
The binary package is called libnss-mdns
--
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
ubun
I seem to be having this problem but there is no package nss-mdns - I
know I had to change the nsswitch.conf to attempt to run Sugar at one
time, what package can I reconfigure to restore default settings?
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchp
excellent news!!
--
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
** Changed in: nss-mdns (Debian)
Status: Unknown => Unconfirmed
--
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.
--
** Bug watch added: Debian Bug tracker #414569
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414569
** Also affects: nss-mdns (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414569
Importance: Unknown
Status: Unknown
--
mdns listed in nsswitch.conf causes excessi
WOW! The real cause is finally known. Lets hope for a quick bug fix and
a backport to feisty.
--
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 c
This is actually due to nss-mdns not avahi directly
** Changed in: nss-mdns (Ubuntu)
Sourcepackagename: avahi => nss-mdns
--
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 Ub
I'm attaching a small C program to demonstrate the issue. It attempts
to reverse map the address 255.0.0.0, which is within a reserved range
and therefore does not have a reverse mapping.
On my Feisty system, it takes about five seconds to run (with the
unmodified /etc/nsswitch.conf). On my othe
"Me too". I just spent half a day tracking down why my Django development
server
running under Feisty was taking 20 seconds to serve a simple web page to
another
machine on the same LAN, and finally tracked it down to this issue.
Specifically,
the client machine was on a private network (IP
The problem is that DNS often responds faster than mDNS. However, if a
DNS server is *not* present, everything would slow down greatly :/
--
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
try downgrading avahi daemon to edgy one - helped for me
Stu
- Original Message
From: Jaya <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 6:16:41 PM
Subject: [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for
dns lookups
This so
This solution worked for me as well. I was experiencing slow pings, email
connections, etc. after installing Feisty. Editing /etc/nsswitch.conf with,
hosts: files dns
seems to have resolved all these issues.
I did not notice any slow down with Edgy. I checked /etc/nsswitch.conf in my
Edgy, str
Thanks a lot Adam.
When I was looking at fixing this (before I found this thread)
I changed my hosts file from:
127.0.0.1 localhost
127.0.1.1
to:
127.0.0.1 localhost
127.0.1.1
Would that possibly create the timeout error? Otherwise I'm pretty standard
Feisty over a wireless network to a rout
For downloading a single file, it isn't necessary to continually do
DNS lookups, only at the beginning. If that screenshot represents one
file being downloaded, then it's probably a different problem.
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchpad.n
Herei s my network use while downloading in Firefox
** Attachment added: "Screenshot-System Monitor.png"
http://librarian.launchpad.net/7404879/Screenshot-System%20Monitor.png
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.launchpad.net/bugs/94940
You rece
Can someone please confirm that the solution
hosts: files mdns4_minimal [NOTFOUND=return] dns
is the best one.
My network performance in Feisty still a little off and below same set-up in
Dapper
Thanks
Stu
--
mdns listed in nsswitch.conf causes excessive time for dns lookups
https://bugs.lau
I thinkt the problem is, is that Ubuntu lacks a 'network' strategy completely.
There is no network-team or something of that kind.
What they need to focus on:
- fairness scheduling (i.e. torrents should wait for firefox' http-requests)
- zeroconf (i.e. automatic file-sharing with other locally
FYI, this also may be a problem in Debian. I checked /etc/nsswitch.conf
on my testing/unstable system and it was set to the same as is default
in Feisty. I have wondered for a long time why my DNS lookups take so
long sometimes. I removed "mdns4"; hopefully that will help.
--
mdns listed in ns
The problem occurs with making ssh-connections. According to strace it
tries to do a reverse lookup of the host I connection too. That host is
a dialup which I cannot be reverse-resolved (which is weird - but
despite this all worked fine with edgy..)
When changing the file to hosts: files dns it w
I have this problem too. It's very annoying. I got my IP from a "AVM Fritz Box
WLAN" router. The AVM guys do a good work and are not to blame that they don't
offer DNS lookup .. I think ..
Perhaps this problem will occur in very much home-network use-cases - those
people which Ubuntu is mainly
Apparently the usual cause for this is having no reverse DNS setup
--
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.
--
ubu
I was going crazy trying to figure out why my "network" was so slow.
This suggestion:
hosts: files mdns4_minimal [NOTFOUND=return] dns
improved things a great deal. It's a bit disconcerting that this has
found its way into the production release, though, as tracking it down
was not a simple
actually I detailed the results of that test in the initial post. I
found no relief with the live containing any references to mdns. The
only way I got my time down to a tolerable amount was to eliminate all
references to mdns and have only files and dns on the line. Then my dns
response returned t
I'm experiencing this too. Martin, if I use that setting you suggested,
my delay improves. The ssh timeout went from about 15s to 5s. If I
remove mdns from the line entirely it's 3s.
However, without mdns I can't ping .local hostnames.
My original line looked like:
hosts: files mdns dns
Now i
I was just pointed to
http://lists.freedesktop.org/archives/avahi/2007-March/001007.html
If you change nsswitch.conf to
hosts: files mdns4_minimal [NOTFOUND=return] dns
do the timeouts disappear then?
** Changed in: avahi (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassign
95 matches
Mail list logo
