This is fixed in Ubuntu 20.04 with nss-mdns 0.14 and later which does
proper split horizon handling.
** Changed in: avahi (Ubuntu)
Status: Triaged => Fix Released
** Changed in: nss-mdns (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
** Summary changed:
- How Can I Buy Soma Online? | Order Carisoprodol Online
+ Avahi daemon prevents resolution of FQDNs ending in ".local" due to false
negatives in the detection of ".local" networks
** Description changed:
Install Kubuntu Feisty
Set the ip address to dhcp for eth0
** Description changed:
Install Kubuntu Feisty
Set the ip address to dhcp for eth0 (ethernet port)
make sure the host name and domain name are set
Hostname computer1
DomainName mydomain.local
allow DHCP to assign the IP address
Ensure the computer details are registered in DNS
I guess I am wrong about the "upstream security hole" thing. But I don't
know why you would use mDNS for serious security anyway.
mdns_minimal already causes a 4-second fallthrough (if AVAHI is disabled
at least).
So Lennart is ranting and screaming only about the [NOTFOUND=return]
line?
As if
Apple, whose OS X Yosemite (10.10) will not even resolve DNS when
internet is down ("private networks don't exist"), simply chose the
wrong name for something that is basically only used by machines.
Their ".local" is not meant for manual use.
They could just as easily have called it ".mdns" or
Ubuntu 14.04 is still affected.
Either the default nsswitch.conf has to be updated to use dns even when
mdns fails or nss-mdns has to be patched to return NSS_STATUS_UNAVAIL
instead of NSS_STATUS_NOTFOUND even for .local domains.
** Also affects: nss-mdns (Ubuntu)
Importance: Undecided
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/80900
Title:
Re #43: the rest of the world (android, iphone, os x, ...) does fallback
to dns when mdns fails though! Maybe that's something to consider.
Also most of the points mentioned there are simply not true when DNS is
used only as a fallback for .local domain when mDNS fails.
--
You received this
** Changed in: avahi (Debian)
Status: Unknown = 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/80900
Title:
Avahi daemon prevents resolution of FQDNs ending in .local due to
** Changed in: avahi (Debian)
Importance: Unknown = Undecided
** Changed in: avahi (Debian)
Status: Fix Released = New
** Changed in: avahi (Debian)
Remote watch: Debian Bug tracker #393711 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: avahi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393711
Importance: Unknown
Status: Unknown
--
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:
Will Rouesnel wrote:
Switching it to
hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4
fixes it by having DNS get checked first.
Please see Lennart Poettering's comments at avahi.org
http://avahi.org/wiki/AvahiAndUnicastDotLocal
and in Debian bug report #393711
** Summary changed:
- problems resolving fully qualified domain names in environments where .local
is used as a TLD
+ Avahi daemon prevents resolution of FQDNs ending in .local due to false
negatives in the detection of .local networks
--
You received this bug notification because you are a
13 matches
Mail list logo
