Ask Your Question

Unable to resolve names of network computers

asked 2014-05-12 06:48:11 -0600

TheGameSquid gravatar image

updated 2014-05-12 10:34:32 -0600

I've just installed Fedora 20 on a physical machine (a new laptop) for the first time. I'm used to working with Linux on a bunch of virtual machines, but now that I've got it running on physical hardware I'm experiencing some issues.

I'm able to ping my Fedora 20 laptop from my Windows 7 gaming PC, but only using the .local suffix. So:

Pinging from my Linux laptop to my Windows Desktop:

ping: unknown host HOME-DESKTOP

[robin@HOME-LAPTOP ~]$ ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from ( icmp_seq=2 ttl=64 time=0.020 ms
64 bytes from ( icmp_seq=3 ttl=64 time=0.021 ms

Pinging from my Windows Desktop to my Linux Laptop:

C:\Data>ping HOME-LAPTOP
Ping request could not find host HOME-LAPTOP. Please check the name and try again.

C:\Data>ping HOME-LAPTOP.local

Pinging HOME-LAPTOP.local [] with 32 bytes of data:
Reply from bytes=32 time=3ms TTL=126
Reply from bytes=32 time=3ms TTL=126
Reply from bytes=32 time=3ms TTL=126
Reply from bytes=32 time=4ms TTL=126

Ping statistics for
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 4ms, Average = 3ms

Here is the output of the hostname, domainname and dnsdomainname commands on the Linux laptop

[robin@HOME-LAPTOP ~]$ hostname
[robin@HOME-LAPTOP ~]$ domainname
[robin@HOME-LAPTOP ~]$ dnsdomainname

My hostfile is configured as follows: HOME-LAPTOP HOME-LAPTOP.localdomain localhost localhost.localdomain
::1 HOME-LAPTOP HOME-LAPTOP.localdomain localhost localhost.localdomain

My /etc/resolv.conf only has entries for the two DNS servers provided by my ISP.

  1. I don't understand where the .local suffix is coming from. Where is this defined, and is it possible to change this?
  2. I don't understand why my Windows machine can resolve the hostname of my linux laptop, but not the other way around.

EDIT (Extra info): The environment I'm testing this is in is a very, very simple home setup with router provided by ISP, not domain, no DNS server of my own etc. This is a bare-bones network environment.

edit retag flag offensive close merge delete


Does your Linux installation have "avahi" installed? My default installation of Fedora 20 (which included Gnome Desktop) installed avahi as a dependency, which opens a hole in the firewall (UDP 5353) and responds to my hostname with the ".local" suffix.

This is something that's tripped me up before in the past. I seem to always work through the issue, but never document it, so I keep having to reinvent the wheel each time. I'd like to help you identify what's going on here and document for my own benefit...

:) John

jcall gravatar imagejcall ( 2014-05-14 16:22:34 -0600 )edit

1 Answer

Sort by » oldest newest most voted

answered 2016-09-25 19:18:56 -0600

Aeyoun gravatar image

updated 2016-09-25 19:20:45 -0600

Windows doesn't currently support mDNS (the .local domains), but Microsoft is slowly adding it to Windows 10. Instead of mDNS, you have to rely on other local network discovery protocols such as NBNS or LLMNR.

Instead of messing with all of that you can rely on your router’s DNS server and DHCP to discover devices over DNS. This will be way more reliable and work with all devices and operating systems. Logon to your router and configure your DHCP to assign a search domain. Assuming you have a somewhat sensible home router, all your machines should be discovererable over DNS with <hostname>.<search-domain> the next time your devices renew their DHCP leases (usually within a day or a reboot).

edit flag offensive delete link more

Question Tools



Asked: 2014-05-12 06:48:11 -0600

Seen: 2,182 times

Last updated: Sep 25 '16