Why Does the Same mDNS Name Resolve to Different Devices Across Home VLANs?

Eva Wong

IceWhale author

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Why Does the Same mDNS Name Resolve to Different Devices Across Home VLANs? - Zima Store Online

The same mDNS name can resolve to different devices across VLANs when each segment sees a different set of local or reflected announcements.

In a ZimaSpace home network, NAS services, Home Assistant, printers, speakers, and containers may advertise .local names on separate trusted and IoT VLANs. mDNS is link-local by design, so a reflector or repeater decides which announcements cross the router. Duplicate hostnames, asymmetric reflector interfaces, and stale caches can make two clients receive different answers for the same label.

Confirm mDNS Is Being Reflected Across Routed VLANs

Compare the same query on each VLAN and inspect which interfaces the reflector listens to.

A focused openwrt homelab blog on mDNS needs a reflector across routed networks helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

If one VLAN never sees the other segment’s announcements, fix reflector scope before investigating DNS caches.

Check Which VLANs Are Allowed to Send Discovery Traffic

Firewall policy must allow the discovery path you expect without opening unrelated unicast access.

A focused homelab network build log on mDNS and DNS need deliberate inter-VLAN rules helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

Keep service discovery rules separate from broad VLAN forwarding so troubleshooting does not destroy segmentation.

Verify the Reflector Is Running on the Right Interfaces

A reflector attached to only one VLAN can create partial visibility that looks like inconsistent name resolution.

A focused homebridge and avahi guide on Avahi can reflect records between selected VLAN interfaces helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

List reflector interfaces and remove accidental WAN or guest segments from the reflection set.

-15% OFF

ZimaBoard 2 - Mini Home Server for Your Big Idea

Single board computer zimaboard2

Separate mDNS From Other Discovery Protocols

Chromecast and some home devices combine mDNS with other multicast or unicast ports.

A focused home assistant networking walkthrough on cross-VLAN discovery can require more than mDNS helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

If the name resolves but the service still fails, test the app’s actual data ports instead of adding more mDNS repeaters.

Check the Home-Server Container Network

Home Assistant or another discovery service running inside Docker may not see the same multicast interfaces as the host.

A focused homelab kubernetes article on containerized Home Assistant needs deliberate cross-VLAN multicast reachability helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

Compare a host-level mDNS query with the query inside the container namespace before editing router rules.

Test for Duplicate Names and Cached Answers

Two devices advertising the same .local hostname can be visible on different VLANs depending on reflection and cache timing.

A focused home-lab networking article on mDNS across VLANs depends on controlled reflection helps isolate this branch because it addresses the same micro-problem instead of only defining the underlying protocol.

Rename duplicates, flush only the test client cache, and repeat captures on both VLANs. The correct result is one stable owner for each required name.

Re-Test the Exact Home-Server Path

After changing one variable, repeat the same NAS or self-hosted workflow from the same client instead of switching to a different test that may use another path.

The related ZimaSpace guide on the adjacent home-server network path helps keep the final verification tied to the same self-hosted environment.

The fix is complete only when the original symptom stays resolved after reconnect, service restart, and a second controlled transfer or request.