| Click here to return to the 'Create the illusion that Bonjour works over a VPN' hint |
It even picks up the troubled Mac (which appears as 'Javan's MacBook Pro' thanks to bonjour) and appear in both the sidebar and the Network folder. Before shots get fired, Yosemite has nothing to do with this. Jan 16, 2018 A simple program called Bonjour Browserallows you to quickly browse all of the Bonjour-enabled devices on your network. If you use a Mac firewall, you’re going to see popups about mDNSResponder. Blocking this process from accessing the network prevents Bonjour from working, which makes it harder to use your local network. Sep 03, 2014 If you're trying to reach out from (or back in to) a Mac running OS X 10.10 Yosemite, Developer Preview, you may have found that your Bonjour networked machines aren't resolving. This is because the mDNSResponder and mDNSResponderHelper are disabled (for some reason.) To re-enable them, you need to edit the com.apple.mDNSResponder.plist.
Why don't you just use 'server' and talk to http://server instead?
A.
(whose intuition says that mucking with Bonjour's namespace is a questionable practice)
I've been in more than a few design agencies that use Mac OS X machines as their server computers for this, that, or the other thing. As a result, most of these services are accessible via Bonjour (since few of these companies set up proper DNS…). So the point is not to force a remote machine into a local namespace, but rather to accommodate remote machines with Bonjour-style names, which are a) not always remote and b) typically use '.local' as their TLD anyway.
---
-Meitar Moscovitz
Professional: http://MeitarMoscovitz.com/
Personal: http://maymay.net/
Or, from the README: http://strange.nsk.no-ip.org/projects/mbridge/
P.
I am using OpenVPN running in bridged mode, and connecting using Tunnelblick. Bonjour-style names work fine. The remote computers all show up in Bonjour Browser right when the VPN connects, and you can ssh some-computer.local without a hitch.
Yeah, OpenVPN is by far my favorite VPN solution. However, most people who use Macs and a VPN are using the Apple-provided VPN server which only does PPTP or L2TP/IPSec tunneling. OpenVPN uses SSL to create the secure tunnel and is generally a more configurable product…. The point still stands, though, that without 'esoteric networking knowledge' you'll probably find mDNS queries blocked by a VPN.
---
-Meitar Moscovitz
Professional: http://MeitarMoscovitz.com/
Personal: http://maymay.net/
However, going digging in to the static files in /etc (many of which are ignored or deprecated in OS X) is seen as somehow (for want of a better word) unesoteric? Yeah sure, it'll work ... until it doesn't.
I'm not laughing, I'm just puzzled why you'd go to all this effort to avoid learning something useful?
You make a good point. I'm not trying to avoid learning something useful, I just haven't learned it yet and this was a solution that works for my admittedly simple situation. Also, I suppose it depends on what 'estoric' means to you. Messing with /etc/hosts is far less esoteric to my mind than mDNS if only because it is more primitive.
---
-Meitar Moscovitz
Professional: http://MeitarMoscovitz.com/
Personal: http://maymay.net/
Bonjour For Mac Yosemite Download
Hamachi is not open source and is found at www.logmein.com . The Mac version is still 0.9.x, requires a separate tunneling driver (linked from the download section), and has no native GUI.
This is probably obvious to most people, but I just wanted to mention that it seems as though Geeklog has eaten the backslashes in parts of this post. Specifically, the line that reads
C:WINDOWSsystem32driversetchosts
should read: C:WINDOWSsystem32driversetchosts
Also there is a minor typo in the original post. Instead of 192.168.0.100, the IP address should have read 192.168.2.100. :)
---
-Meitar Moscovitz
Professional: http://MeitarMoscovitz.com/
Personal: http://maymay.net/
This is nice and all but it's probably better to encourage folks to use internal DNS instead. From a best practices perspective. . . .this might be fine for joe schmoe's home network but for buisness use. . NO. Suck it up and use dns.
If it ain’t broke, don’t fix it is a rule that Apple may wish it had heeded when it released Yosemite back in 2014. Why? Because Apple’s famed ‘it just works’ ease of use took a serious hit, at least when it came to networking. When it launched Yosemite, Apple ditched a process called ‘mDNSResponder’, which was a key part of Bonjour, the auto-discovery system for devices on a network. Without mDNSResponder, Bonjour ran into a heap of trouble on lots of Macs. And it wasn’t long before users started complaining of bugs in the system.
Bonjour For Mac Download
What is mDNSResponder and why is it on my Mac?
As many users discovered when they installed Yosemite, mDNSResponder is a critical part of the Bonjour networking protocol. Bonjour is the thing that allows your Mac to ‘see’ other devices like computers, printers, and storage devices on your local network and connect to them easily. If you’ve ever noticed a printer or computer in the sidebar in the Finder that just appeared there, that’s Bonjour — it ‘discovered’ it on your local network and allowed you to see it so you can connect if you want. Noticed an app pop-up on the Dock on your Mac when you use it on an iPhone or iPad close by? That’s Bonjour too. And mDNSResponder is key to Bonjour working properly.
Specifically, mDNSResponder is a daemon that’s responsible for discovering services running on other devices on the local network. It also handles DNS requests for services that need to connect to the internet. Apple replaced it with a service called ‘discoveryd’ process in Yosemite and things went badly wrong — perhaps no surprise given than mDNSResponder had been fine-tuned for over a decade and that networking has always been one of the most troublesome parts of macOS.
Did you know?
Ars Technica reported that when Apple put mDNSResponder back into macOS, it was able to close 300 separate bug reports. That shows you just how much an effect removing it had on macOS and demonstrates that even Apple gets it wrong sometimes.
What’s the problem with mDNSResponder?
Some Mac users have reported that mDNSResponder’s network usage is causing problems on their Mac, and that it’s flooding the network with ‘junk packets’ — traffic that occupies bandwidth but serves no purpose. They discover this using tools that monitor network traffic. For that reason, they want to remove or disable it.
However, removing mDNSResponder will break Bonjour and make discovering and connecting to other devices on the network impossible. You could disable Bonjour altogether, but that would mean manually entering details for every device you want to connect to and make any services that rely on auto-discovery, like Hand-off and Continuity, unusable.
Tip: If you face any issues or see alerts about the mDNSResponder, flush your DNS cache with a free tool in CleanMyMac X. It helps resolve some server connection problems.
Get a free version of the app here
After you install the app, click Maintenance and tick Flush DNS Cache.
If you’ve noticed that your Mac has become sluggish, it can be difficult to work out what the problem is. You could use Activity Monitor to identify mDNSResponder, but all those processes are difficult to understand. CleanMyMac X can help.
CleanMyMac X has a menu item that you can keep active even when you quit the main app. It allows you to monitor CPU usage, network activity, and free up memory. You can get more information on resource hogs within the menu item, and also quit apps that are too demanding.
The main CleanMyMac X application has an optimization tool that also highlights heavy consumers of resources, allowing you to take control of them. And it can identify and shut down applications that have stopped responding due to a problem.
As you can see mDNSResponder isn’t a virus, as some people think when they see it running in the background. It’s an essential component of macOS that allows the automatic discovery of devices on the local network in Bonjour. So you should definitely not try and remove it. If you think it’s making your Mac slow, there’s probably another explanation. And to find out what it is, you can use CleanMyMac X’s arsenal of tools. Once you’ve identified the problem, CleanMyMac can help you solve it by freeing up RAM or quitting hung processes.