FS#18278 - [avahi] Zeroconf hostname resolution for .local fails

Attached to Project: Arch Linux
Opened by Erwin Van de Velde (evdvelde) - Wednesday, 10 February 2010, 20:42 GMT
Last edited by Ionut Biru (wonder) - Thursday, 11 February 2010, 11:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When I use avahi-resolve-host-name laptop.local, it returns an IPv4 or IPv6 address, but when using e.g. ping laptop.local, I get 'Unknown host'.
I use following line in nsswitch.conf:
hosts: files mdns_minimal dns mdns
(same result when using mdns4)


Additional info:
* package version(s)
avahi 0.6.25-1
kernel26 2.6.32.8-1
filesystem 2010.01-1
(x86_64)

* config and/or log files etc.
nsswitch.conf: contains 'hosts: files mdns_minimal dns mdns'

Steps to reproduce:
ping a host in the zeroconf .local domain
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 11 February 2010, 11:20 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 10 February 2010, 21:13 GMT
  • Field changed: Summary (Zeroconf hostname resolution for .local fails → [avahi] Zeroconf hostname resolution for .local fails)
  • Field changed: Status (Unconfirmed → Waiting on Response)
I never used avahi, I can not help. Since this package is "Orphaned", maybe is better to post this on forum, and if this is a issue with "packaging" or "upstream" (with link to bugreport/patch) please post here, so I can assing to some dev. Thanks.
Comment by Ionut Biru (wonder) - Wednesday, 10 February 2010, 21:40 GMT
maybe you forgot to do the proper configuration:

http://wiki.archlinux.org/index.php/Avahi#Hostname_resolution
Comment by Erwin Van de Velde (evdvelde) - Wednesday, 10 February 2010, 22:32 GMT
I configured it correctly: please read my post (I added mdns to nsswitch.conf). Furthermore, I checked my configuration with an ubuntu host (same avahi version, same config) where it worked just fine, so this is no upstream issue! Hopefully someone can confirm this bug or tell me a workaround.
Comment by Ionut Biru (wonder) - Wednesday, 10 February 2010, 22:39 GMT
ping naboo.local
PING naboo.local (192.168.0.1) 56(84) bytes of data.

be sure you have nss-mdns installed as it is an optdepends of avahi. not forget about starting avahi-daemon
Comment by Erwin Van de Velde (evdvelde) - Thursday, 11 February 2010, 09:21 GMT
Thank you Ionut, I did not have nss-mdns installed indeed... perhaps it should be a real dependency instead of an optional one? Considering it is 0.09MB big only and avahi really makes a lot more sense with it installed :-)
Comment by Ionut Biru (wonder) - Thursday, 11 February 2010, 11:19 GMT
open a feature request for that

Loading...