Indicates that this is expected and explains your various options: Chrome now requires that we ask users for permission to communicate with our new native messaging host. So, if LastPass does not detect the binary component the first time that you click on the LastPass button, we prompt you for permission.

If you: • Click deny, LastPass will never prompt again • Click accept, LastPass will pop a confirm box stating that if you have not done so yet, you will need to run the universal installer to install the binary component Then: • if you click OK, we redirect to the binary component which downloads in the browser. • if you click Cancel, then we do not download the binary installer.

It turns out the solution was to bounce mDNSResponder: sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist This was obtained by a different coworker from. OS X 10.10.0 – 10.10.3, Yosemite, mDNSResponder doesn't exist in Yosemite (OS X 10.10). You can restart descoveryd instead to fix these issues. Sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist OS X 10.10.4+, Yosemite In OSX 10.10.4 the mDNSResponder has been. So use the first one will work again.

Use Legacy Browser Support (LBS) with the latest stable release of Chrome. Additionally, install the Legacy Browser Support - native host add-on for your users. Without this package the Extension will not be able to open the alternative browser. I have tried a variety of websites for how to get Google Chrome Browser Source Code. Mac and Linux. – Rob Kennedy Dec 1 '11 at 18:12. Every time you call Chromium 'Chrome', a kitten dies. – Webveloper Oct 13 '14 at 11:06 show 2 more comments. Where to host an Open Source Project: CodePlex, Google Code, SourceForge?

@dkagedal This is actually as good an answer as we're going to get - this happens because your mac caches the DNS entries to avoid hitting your DNS server (likely your router) for every DNS lookup - which happens a lot. This cache is necessary, and good, but it would be nice if there were better behavior when an entry is not found (I consider this a bug). In any case, there is some timeout in the cache; when I waited 10 minutes or so on my machine, this situation resolved itself. For the majority of users, the existing behavior is fine, so is not likely to be changed by Apple anytime soon. – Nov 12 '12 at 17:00 •. I've experienced the same problem And while restarting mDNSResponder does seem to 'work', restarting it a couple of times every hour sort of sucks.

So, for now, I've 'solved' the problem by running locally. To do that: • Build dnsmasq (download the tgz and make or brew install dnsmasq) • Put this in a dnsmasq.conf file: resolv-file=resolv.conf user=nobody group=nobody interface=lo0 cache-size=1024 • Put this in a resolv.conf file that is in the same directory as the dnsmasq.conf file (nb: not /etc/resolv.conf): nameserver 8.8.8.8 nameserver 4.2.2.1 nameserver 4.2.2.2 • Run dnsmasq with sudo dnsmasq --no-daemon --log-queries -C dnsmasq.conf.

The output should look something like. Dnsmasq: reading resolv.conf dnsmasq: using nameserver 4.2.2.1#53 dnsmasq: using nameserver 4.2.2.2#53 dnsmasq: using nameserver 8.8.8.8#53 dnsmasq: read /etc/hosts - 6 addresses • Open Network Preferences and make sure that 127.0.0.1 is the only DNS server (network preferences -> advanced -> DNS -> add 127.0.0.1) Things should begin to work nicely again. Once things are working, you can run dnsmasq without the --no-daemon and --log-queries options, so it will start in the background and you don't need to keep a Terminal window open. For future readers, I found it easiest to just ssh into my box at work, determine which IP's it had for name servers, and then hardcode those IP's into my resolv.conf below 8.8.8.8 (googles DNS server). That allows all non company names to resolve properly without having to go through company servers, which I find useful for privacy and speed. As far as hardcoding goes, those IP's aren't going to change any time soon, and if they do, I won't be the only one affected and it should be trivial to edit two lines. – Apr 16 '16 at 6:39 •.

Name resolution under OSX (and UNIX in general) is taken from the IP addresses of the DNSs in the file located in /etc/resolv.conf (which OS X automatically generates as far as I can remember). Since you've tried virtually anything that comes to my mind, I'd like to ask you: • Can you ping the DNS you want to use?