# 🛰 Disable mDNS in Your Browser
> **A one-time, 30-second setup.** Flip a single browser setting and your bot's live video will connect for good.
---
## 🤔 Why this is needed
ZRSense robots stream live video and accept commands over **WebRTC** — a peer-to-peer connection between your browser and the bot. To find each other on your network, the browser and the bot exchange a list of IP addresses called **ICE candidates**.
For privacy, modern browsers replace your computer's local IP with an mDNS hostname that looks like `abc123-def456.local`. The ZRSense bot can't resolve those `.local` names, so the connection fails before video starts.
**The symptom you'll see:** a spinning *"Connecting…"* that never finishes.
> ✅ **Once you flip the setting below, you're done forever.** It survives browser updates and restarts.
---
## 🌐 Pick your browser
> **Tip:** Click the section for the browser you use. Each one takes under a minute.
[details="🟦 Google Chrome — ~30 sec"]
**1.** Copy this address:
chrome://flags/#enable-webrtc-hide-local-ips-with-mdns
**2.** Paste into Chrome's address bar and press **Enter**.
**3.** Change the dropdown from **Default** (or **Enabled**) → **Disabled**.
**4.** Click the blue **Relaunch** button at the bottom of the page.
✓ Done.
[/details]
[details="🟦 Microsoft Edge — ~30 sec"]
**1.** Copy this address:
edge://flags/#enable-webrtc-hide-local-ips-with-mdns
**2.** Paste into Edge's address bar and press **Enter**.
**3.** Change the setting from **Default** / **Enabled** → **Disabled**.
**4.** Click the blue **Restart** button.
✓ Done.
[/details]
[details="🦁 Brave — ~45 sec"]
**1.** Copy this address:
brave://flags/#enable-webrtc-hide-local-ips-with-mdns
**2.** Paste into Brave's address bar and press **Enter**.
**3.** Change the setting from **Default** / **Enabled** → **Disabled**.
**4.** Click the blue **Relaunch** button.
> ⚠ **Brave also blocks WebRTC through its shield.** If video still won't load after the flag change, click the Brave **Shield** icon (lion 🦁 in the address bar) and toggle **WebRTC** to allow ZRSense.
✓ Done.
[/details]
[details="🦊 Firefox — no restart"]
**1.** Type `about:config` into Firefox's address bar and press **Enter**.
**2.** Click **Accept the Risk and Continue** if Firefox warns you.
**3.** In the search box, paste this preference name:
media.peerconnection.ice.obfuscate_host_addresses
**4.** Click the toggle on the right to flip **true → false**.
**5.** No restart needed — open a new tab and connect.
✓ Done.
[/details]
[details="🍎 Safari (Mac / iPhone / iPad) — nothing to do"]
Safari doesn't have this restriction by default.
✓ Open the ZRSense page and connect — no setting to change.
[/details]
---
## 🛡 Is it safe to turn this off?
**Yes — completely safe.** A quick breakdown of what's actually happening:
| | What changes | What does *not* change |
|---|---|---|
| 🔒 | Sites using WebRTC can see your **local network IP** (e.g. `192.168.1.42`) | Your **public internet IP** is unchanged. Hidden either way. |
| 🌍 | Local IP is only meaningful inside your home network | Cannot identify your location, track you, or be used outside your LAN |
| 🔐 | Banking, password manager, browsing history, files — none of it is touched | This is a tiny WebRTC-specific toggle |
| ↩ | Reversible in 10 seconds — flip it back if you ever change your mind | No system-level changes |
> 💡 Many tools that use WebRTC for local communication — smart-home apps, peer-to-peer file transfer, LAN conferencing — need this exact setting disabled. ZRSense is one of them.
---
## ✅ How do I know it worked?
Open the ZRSense **Camera** page and click **Connect**. Within ~5 seconds you should see live video.
If it still says *"Connecting…"* after 30 seconds:
- Double-check the flag is set to **Disabled** (not Default).
- Make sure you clicked the **Relaunch** / **Restart** button — the flag won't take effect until the browser restarts.
- (Brave only) check the Shield icon for WebRTC.
---
## 🛣 Why doesn't ZRSense just fix this for me?
The flag is a browser-level privacy default we can't change from a web page. The long-term fix is to teach the bot how to resolve `.local` hostnames itself — that's on our roadmap, but it's a significant firmware change. Until then, this 30-second tweak gets you up and running.
---
> 🎉 **You're all set.** Welcome to ZROne.