[Bug 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks

[xennex82]

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 he decides what NSS does. His is a plugin. A plugin is a peer to
other plugins; not one plugin is more important than the others;

the plugin is just that, the configuration is up to the end user (or the
bigger system).

He acts as if /etc/nsswitch.conf now belongs to his package.

His PulseAudio also configures itself in the same way as authorative
with ALSA. Same idea, repeats itself.

  "If PulseAudio module is loaded, set it to be the ALSA default
device".

  What?

  What if some other module wanted to do the same?

So NSS is to Lennart just an annoyance, an archaic system that doesn't
make him the most important person in the world and then he starts
saying "fuck yous" to get his way.

He wanted his package to be orphaned and renamed, as if he holds a
trademark to "mdns".

As if he holds a trademark to "libnss".

Nothing about that is "Lennart".

That's the least trade-markable name in the history of trademarkable
names.

And then he starts ranting "You don't give a fuck about people and you
think it's about you".

But everything is always about Lennart.

What Lennart wants.

What Lennart decides.

What Lennart says is best.

Quite remarkable that you can think "libnss-mdns" is somehow a
trademarkable name.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nss-mdns in Ubuntu.
https://bugs.launchpad.net/bugs/80900

Title:
  Avahi daemon prevents resolution of FQDNs ending in ".local" due to
  false negatives in the detection of ".local" networks

Status in avahi package in Ubuntu:
  Triaged
Status in nss-mdns package in Ubuntu:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  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 for
  mydomain.local...

  computer names registered in DNS (FQDN) 
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local

  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.

  if I issue the following comands on computer2 or computer3, it works
  correctly:

  ping computer2      (response received - ping good)
  ping computer3      (response received - ping good)
  ping computer2.mydomain.local       (response received - ping good)
  ping computer3.mydomain.local       (response received - ping good)

  if i issue the same commands from the feisty box (computer1), these
  are the results..

  ping computer2       (response received - ping good)
  ping computer3       (response received - ping good)
  ping computer2.mydomain.local       (unknown host)
  ping computer3.mydomain.local      (unknown host)

  for some reason if you try to ping the fully qualified domain name on
  feisty, it cant resolve it, yet it can resolve it using both static IP
  Addressing and DHCP addressing on Dapper. (i set the IP to static as
  well for the test) Static and DHCP on Dapper works fine. Static and
  DHCP wont resolve fully qualified domain names on Feisty. (computer1,
  computer2 and computer 3 are all Kubuntu machines. DNS Server is a
  Windows 2003 Server (that will be changed a kubuntu server very soon
  though!)

  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.

  cheers

  Rod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+subscriptions