Bug 1023214 - unable to resolve OS X bonjour hostname
unable to resolve OS X bonjour hostname
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: avahi (Show other bugs)
20
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-24 18:09 EDT by Chris Murphy
Modified: 2013-10-25 00:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-25 00:33:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Murphy 2013-10-24 18:09:24 EDT
Description of problem: OS X can resolve Fedora hostnames, however Fedora cannot resolve OS X hostnames.


Version-Release number of selected component (if applicable):
avahi-0.6.31-21.fc20.x86_64
nss-3.15.2-2.fc20.x86_64


How reproducible:
Always

Steps to Reproduce:
1. From Fedora, ssh chris@ming.local

Actual results:
ssh: Could not resolve hostname ming.local: Name or service not known

Expected results:
ssh should ask for my password and connect me.

Additional info:

Fedora is f20s.localdomain 192.168.1.144
OS X is ming.local 192.168.1.126

If I reboot Fedora to OS X where it is named ming2 at the same 192.168.1.144 address # ssh chris@ming.local does work.


Fedora:
[chris@f20s ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1e:c2:1d:50:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.144/24 scope global dynamic p5p1
       valid_lft 76722sec preferred_lft 76722sec
    inet6 fe80::21e:c2ff:fe1d:507e/64 scope link 
       valid_lft forever preferred_lft forever
3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether fe:54:00:0c:5d:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr0 state UNKNOWN qlen 500
    link/ether fe:54:00:0c:5d:20 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe0c:5d20/64 scope link 
       valid_lft forever preferred_lft forever



OS X:
ming:~ chris$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether e0:f8:47:39:5d:de 
	inet6 fe80::e2f8:47ff:fe39:5dde%en1 prefixlen 64 scopeid 0x4 
	inet 192.168.1.126 netmask 0xffffff00 broadcast 192.168.1.255
	media: autoselect
	status: active
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
	ether c8:2a:14:03:fd:7a 
	media: autoselect (none)
	status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
	ether 02:f8:47:39:5d:de 
	media: autoselect
	status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
	lladdr 70:cd:60:ff:fe:bf:5a:d6 
	media: autoselect <full-duplex>
	status: inactive
Comment 1 Chris Murphy 2013-10-24 18:10:48 EDT
So the summary is that OS X to OS X works. OS x to Fedora works. Fedora to OS X does not work, I have to ssh using IP address.
Comment 2 Chris Murphy 2013-10-25 00:33:27 EDT
Package nss-mdns was not installed. Installing it fixes this problem. Uncertain why it's not installed by default.

Note You need to log in before you can comment on or make changes to this bug.