[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2013-02-05 Thread Thomas Hood
Will wrote: > hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4 I don't see the point of putting "mdns4_minimal" before "mdns4". Just "mdns4" should be equivalent and faster, but maybe I'm missing something. Jeremy wrote: > The nsswitch.conf edit fixed it for me. > Can we please get this as

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2013-02-04 Thread Jeremy Lincicome
I ran into this bug as well on 12.04.2. The nsswitch.conf edit fixed it for me. Can we please get this as default configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/80900 Title: problems r

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2012-06-20 Thread Will Rouesnel
Just ran into this myself with 12.04. The problem is nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 which means looks up check hosts, mdns and if mdns reports a not found then it doesn't go to DNS. Switching it to hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2011-10-03 Thread The Card Cheat
Had this problem and my boss had this simple fix. none of the more complicated solutions worked for me anyway open /etc/default/avahi-daemon change AVAHI_DAEMON_START=1 to AVAHI_DAEMON_START=0 stop service sudo /etc/init.d/avahi-daemon restart -- You received this bug notification because you

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2010-11-24 Thread hyper_sonic
Yes, I encountered the same problem. But I fixed it. In /usr/lib/avahi/avahi-daemon-check-dns.sh I replaced string here: # OUT=`LC_ALL=C host -t soa local. 2>&1` # if [ $? -eq 0 ] ; then #if echo "$OUT" | egrep -vq 'has no|not found'; then # return 0 #fi # else. # Checking the

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2010-11-11 Thread dahias
yep - please increase importance. it's annoying for all the poeple using ubuntu in business. not all will find the workaround for this bug quickly. -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 You received

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2010-08-04 Thread enoch
Bug still present in Lucid ... Same symptoms, same resolution : by deactivating avahi or by fixing the nsswich.conf -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 You received this bug notification because y

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-11-05 Thread Noesis
I would like to second the request for a different default nsswitch.conf. Frankly, I don't understand why the default is: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 This says if something is not found in the .local TLD don't bother looking in dns. I would suggest either pu

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-06-26 Thread Doug
Please increase the importance of this issue, it really needs to get fixed. -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-06-25 Thread scottuss
Apologies for double post. Also, can we get this bumped up from medium importance? I'd say this is a pretty big issue considering many organisations use .local -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 Y

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-06-25 Thread scottuss
We found that disabling the Avahi daemon helped. The problem we found seems to lie in the fact that whenever we tried to do a lookup / ping for a host on the .local domain, the system would append .local to it again. Therefore when we did: ping ourhost.companyname.local we actually got ping ourho

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-06-25 Thread scottuss
We found that disabling the Avahi daemon helped. The problem we found seems to lie in the fact that whenever we tried to do a lookup / ping for a host on the .local doman, the system would append .local to it again. Therefore when we did: ping ourhost.companyname.local we actually got ping ourhos

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-06-12 Thread Chris Gilbert
This bug is causing a lot of problems. As the avahi-daemon is enabled by default, you need a great deal of knowledge to know what is going on here. For instance, our Microsoft network in the office uses the popular .local pseudo domain. When connected to the VPN: ping server - Works fine ping s

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-05-04 Thread Robert Ancell
Bug 327362 is about the daemon being disabled when their ISP DNS has .local in it. -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-05-04 Thread Robert Ancell
** Changed in: avahi (Ubuntu) Status: Confirmed => Triaged -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/bugs/80900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-03-24 Thread sefs
Can it be like this? hosts: files mdns4_minimal dns [NOTFOUND=return] mdns4 So that the dns comes before the notfound so that mdns is checked first then dns? Thanks. -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.launchpad.net/b

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2009-03-09 Thread Alfas
Thanks nitecode. This problem was so annoying. Simple change in /etc/nsswitch.conf hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4 solved the problem. This should fixed in default configuration. -- problems resolving fully qualified domain names in environments where .local is used as a

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2008-06-28 Thread nitecoder
A simple solution to this problem is implied here: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/153644 Changing the /etc/nsswitch.conf file's hosts line from hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 to hosts: files dns mdns4_minimal [NOTFOUND=return] md

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2008-06-03 Thread Loye Young
My company has come up against this problem time and again. Our most reliable solution is to purge avahi-daemon, avahi-autoipd, and libnss- mdns, which allows networking to work automatically. > on a large network avahi plays a large role in finding > shares and printers Printer recognition still

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2008-05-21 Thread mcredz
This probably needs more testing, especially on the Samba side of things before this is accepted as fix. I can't speak on the Samba side myself, as I have no reason to join my *nix machines to our AD, so I don't, but if Samba emulates the lookups that Windows clients perform, this will still break

[Bug 80900] Re: problems resolving fully qualified domain names in environments where .local is used as a TLD

2008-05-16 Thread Nathaniel W. Turner
** Summary changed: - problems resolving fully qualified domain names on Kubuntu feisty + problems resolving fully qualified domain names in environments where .local is used as a TLD -- problems resolving fully qualified domain names in environments where .local is used as a TLD https://bugs.