So far, I have avahi-daemon running on all my Ubuntu machines, partly because it is installed by default. The router I used to have was quite dumb and did not really do anything except DHCP and DHCPv6. I could access the other Linux computers with hostname.local which worked fine for my purposes.

Now I have an AVM FRITZ!Box 7360 which also does some more regarding hostnames as I can access the Linux machines with hostname.fritz.box in my local network as well.

For some reason, I also can do the following now (Linux → Windows):

$ ping martin-pavilion.local
PING martin-pavilion.local ( 56(84) bytes of data.
64 bytes from Martin-Pavilion.fritz.box ( icmp_seq=1 ttl=128 time=0.633 ms

The martin-pavilion is running Windows 8. I do not think that it was accessible via .local previously, and the FRITZ!Box seems to translate the .local into the .fritz.box.

What is happening here? I somewhat got that Zeroconf/Avahi/Bonjour managed to let every computer know about every other one. Does the FRITZ!Box do the same or is this different?

My /etc/resolv.conf is:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
search fritz.box
  • That depends on if FRITZ!Box is configured to provide DNS Via DHCP. Please show me your "/etc/resolv.conf" file. Commented Oct 2, 2014 at 18:49
  • @Tyler the Fritz!Box always provides DNS via DHCP. This is not configurable. You can only enable DHCP/DNS or disable it.
    – Uwe Plonus
    Commented Oct 2, 2014 at 18:58
  • Are you running a DNS Server on Fritzbox?
    – eyoung100
    Commented Oct 2, 2014 at 21:11
  • @eyoung100 the Fritz!Box always runs a DNS server. It serves name resolution for the local net and forwards all other requests to the ISP.
    – Uwe Plonus
    Commented Oct 3, 2014 at 8:05
  • So the FRITZ!Box has a DNS Server and automatically gathers the hostnames of all devices? So I do not need Avahi/Zeroconf/Bonjour any more? Commented Oct 5, 2014 at 15:47

1 Answer 1


The FritzBox home router is using DHCP requests to update the FritzBox's DNS forwarding. Specifically: if there is a hostname option provided in the DHCP request then a hostname.fritz.box DNS record is provided by the FritzBox's DNS forwarding.

This is distinct from mDNS's .local domain. The FritzBox is not a mDNS proxy server.

  • Does this mean in simple words that my tries to ping xxx.local will not work if my router is a fritz.box? I have an mDNS setup on an embedded device, but I am not able to reach it for some reason. Is it because mDNS is not supported in fritz.box? Commented Nov 8, 2020 at 4:04
  • 2
    In simple words: mDNS within a single subnet doesn't need support in the router, so the manufacturer doesn't matter. All that matters is that subnet broadcasts sent by one host are seen by all other hosts. Those broadcasts can sometimes be prevented if "host isolation" or "P2P blocking" is set in the access point. On the FritzBox set "Wireless | Security | The active wireless devices displayed below may communicate with each other".
    – vk5tu
    Commented Nov 9, 2020 at 9:59
  • 1
    Thank you for your reply, this is weird, this option is selected, never the less mDNS does not work in my case for ESP chip. I have to investigate this further. Thank you! Commented Nov 9, 2020 at 11:01
  • @MohammedNoureldin Yes, .local will work, fortunately it does not need the fritz. But you need an mdns responder on your devices. On Linux, it can be done by avahi. On Windows, it needs a policy setting. Afaik ios has it by default (never tried). Android probably can do it only by rooting the thing. Btw, if you have a choice in the future, avoid fritz.
    – peterh
    Commented Oct 6, 2021 at 0:28
  • @peterh Avoid it why? Commented Dec 23, 2021 at 22:07

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .