# Support multicast DNS

**URL:** https://community.muos.dev/t/support-multicast-dns/653
**Category:** Approved
**Created:** [July 29, 2025, 5:41am UTC](https://community.muos.dev/t/support-multicast-dns/653 "2025-07-29T05:41:00Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Nimrod](https://community.muos.dev/user_avatar/community.muos.dev/nimrod/32/1637_2.png) [@Nimrod](https://community.muos.dev/u/Nimrod)
#### Post date: [July 29, 2025, 5:41am UTC](https://community.muos.dev/t/support-multicast-dns/653/1 "2025-07-29T05:41:00Z")

</div>

I haven’t actually set this up on Linux before, but it’s implemented by avahi-daemon so should be easy, but could probably use a hostname option in the config to make it more worthwhile.

Basically, I like to ssh/sftp/etc into my muOS device remotely because that’s usually the easiest way to do some stuff, but it’s always a bit easier to do this when I can use `hostname.local` names rather than having to figure out the IP address.

It would of course also be helpful for anyone using anything requiring a hostname, like the http filebrowser.

---

<div class="post-metadata">

### Author: ![\_krt](https://community.muos.dev/user_avatar/community.muos.dev/_krt/32/489_2.png) [@\_krt](https://community.muos.dev/u/_krt)
#### Post date: [July 29, 2025, 7:01am UTC](https://community.muos.dev/t/support-multicast-dns/653/2 "2025-07-29T07:01:00Z")

</div>

fwiw, in the mean time, you could setup a static DHCP lease for your device or a static IP in muOS and then you can use regular DNS A records.

---

<div class="post-metadata">

### Author: ![Nimrod](https://community.muos.dev/user_avatar/community.muos.dev/nimrod/32/1637_2.png) [@Nimrod](https://community.muos.dev/u/Nimrod)
#### Post date: [July 29, 2025, 8:50am UTC](https://community.muos.dev/t/support-multicast-dns/653/3 "2025-07-29T08:50:33Z")

</div>

True, but I don’t have a local dns server set up so I can’t do split DNS, and don’t really want to put rfc1918 addresses in external a records. Maybe I should just set up pi-hole anyway though… For now I’ll just use local hosts file or type the address (at least it’s reserved in DHCP so shouldn’t change).

---

<div class="post-metadata">

### Author: ![\_krt](https://community.muos.dev/user_avatar/community.muos.dev/_krt/32/489_2.png) [@\_krt](https://community.muos.dev/u/_krt)
#### Post date: [July 29, 2025, 9:02pm UTC](https://community.muos.dev/t/support-multicast-dns/653/4 "2025-07-29T21:02:18Z")

</div>

if you’re managing a hosts file you’re half way to running your own zone files… good excuse to setup internal DNS. fwiw, I think dnsmasq is trivial, unbound is easy, bind is well documented, djbdns is FAST. (I use them all)

---

<div class="post-metadata">

### Author: ![xonglebongle](https://community.muos.dev/user_avatar/community.muos.dev/xonglebongle/32/57_2.png) [@xonglebongle](https://community.muos.dev/u/xonglebongle)
#### Post date: [September 25, 2026, 10:20am UTC](https://community.muos.dev/t/support-multicast-dns/653/5 "2026-09-25T10:20:08Z")

</div>

This is now added in Andromeda amongst other network changes. However please keep in mind that some firewalls and browser combinations may stop this from working it seems.

> **[How to Debug Blocked Requests: Local-Network-Access in Chrome](https://blog.paulserban.eu/post/how-to-debug-blocked-requests-local-network-access-in-chrome/)**
>
> Learn advanced debugging techniques to address issues caused by Chrome's local-network-access checks, including using proper headers and DevTools.

---

<div class="post-metadata">

### Author: ![xonglebongle](https://community.muos.dev/user_avatar/community.muos.dev/xonglebongle/32/57_2.png) [@xonglebongle](https://community.muos.dev/u/xonglebongle)
#### Post date: [September 25, 2026, 10:20am UTC](https://community.muos.dev/t/support-multicast-dns/653/6 "2026-09-25T10:20:44Z")

</div>


