Remembering IP addresses for every device on your home network gets tedious fast, and not every homelab setup justifies running a full DNS server just to access a single new device by name. mDNS with Avahi offers a lightweight alternative, letting devices automatically discover and reach each other using simple .local hostnames with zero central configuration required.

What Is mDNS?

Multicast DNS (mDNS) is a protocol that allows devices on the same local network to resolve hostnames to IP addresses without needing a centralized DNS server at all. Instead, devices multicast queries directly on the local network (“who is myserver.local?”) and the device matching that name responds directly, all happening automatically without any manual DNS record configuration.

What Is Avahi?

Avahi is the standard Linux implementation of mDNS and the related DNS-SD (DNS Service Discovery) protocol, both part of the broader “Zeroconf” (zero configuration networking) family that also includes Apple’s Bonjour, which many people are already familiar with from macOS and iOS devices automatically discovering printers and other devices on a network.

Why Use mDNS Alongside Pi-hole or Technitium

Pi-hole and Technitium work well for network-wide DNS management and ad-blocking, but require you to manually add each new local service as a DNS record. mDNS instead works automatically the moment a device joins the network, with zero manual configuration needed — useful specifically for quick access to individual devices without the overhead of updating a central DNS server’s records for every single new machine.

Installing Avahi

On Debian or Ubuntu-based systems, Avahi is often already installed by default. If not:

sudo apt update
sudo apt install avahi-daemon -y

Setting Your Server’s Hostname

Avahi automatically advertises your device using its configured system hostname, appended with .local. Check or set your hostname:

hostnamectl set-hostname myserver

After setting this, the device becomes reachable on your local network as myserver.local automatically, once Avahi is running.

Verifying Avahi Is Running

sudo systemctl status avahi-daemon

Testing Discovery from Another Device

From another Linux machine on the same network:

ping myserver.local

On Windows, mDNS support may require Bonjour Print Services (bundled with iTunes or available standalone) since Windows doesn’t include native mDNS support by default the way Linux and macOS do.

Advertising Specific Services

Beyond basic hostname resolution, Avahi can advertise specific services running on your device, making them discoverable by other Zeroconf-aware applications. Create a service definition file under /etc/avahi/services/:

xml

<?xml version="1.0" standalone='no'?>
<service-group>
  <name>My Web Server</name>
  <service>
    <type>_http._tcp</type>
    <port>80</port>
  </service>
</service-group>

This allows compatible network scanning tools and applications to automatically discover that your device offers an HTTP service, without needing to know its specific IP address in advance.

mDNS Limitations to Understand

• Local network only – mDNS queries don’t route across network segments or VLANs by default, meaning a device on a separate VLAN () generally can’t resolve .local hostnames on a different segment without additional mDNS reflector configuration
• Not a replacement for proper DNS – mDNS works well for quick, zero-configuration local access, but doesn’t offer the centralized management, logging, or ad-blocking capabilities of a proper DNS server like Pi-hole
• Occasional name conflicts – if two devices end up with the same hostname, mDNS resolution can become ambiguous or inconsistent

Combining mDNS with Your Existing DNS Setup

Many homelab users run both simultaneously without conflict — Pi-hole or Technitium for network-wide ad-blocking and deliberately configured service records, alongside Avahi for zero-configuration convenience when quickly accessing a new or temporary device without wanting to manually add a DNS record for something short-lived.

Final Thoughts

Setting up mDNS with Avahi provides a genuinely convenient, zero-configuration way to reach devices on your home network by name, complementing rather than replacing a proper DNS server for your more deliberately managed, permanent services. For quick access to new devices without the overhead of manual DNS record management, mDNS remains one of the simplest networking conveniences a homelab can have running by default.

Related Posts

• How to Set Up a WireGuard VPN Server on Linux
• How to Set Up Nginx Proxy Manager for Your Home Lab
• How to Set Up Pi-hole with Unbound for Private DNS