The printer or media device may appear in one room with a .local name but not in another VLAN. Understanding the scope of local discovery prevents mistaking it for a device malfunction.
Basic approach
mDNS uses multicast for name resolution on the local link. Normal routing does not mean that this discovery will be automatically moved to different subnets. Corporate networks may require controlled gateways or special discovery policies; these depend on the design of the network manager.
Application steps
- Verify whether the client and target are in the same connection area.
- Review Wi-Fi client isolation and multicast filtering settings.
- Test device access via IP separately from resolving the .local name.
Practical example
If a phone cannot see the meeting room screen when connected to the guest Wi-Fi network, but sees it when switched to the employee network, discovery limit or isolation may be effective. This may also be a designed security behavior.
Interpret the result correctly
Spreading all multicast traffic across all VLANs is not the default solution. Identify the required services and user groups. The display name in the mDNS response can be changed; Do not use this as a physical device ID or trust relationship.
Source and follow-up reading
Protocol or command details: RFC 6762. The steps and example scenario are IPScans editorial narrative.