So, for now, I've 'solved' the problem by running dnsmasq locally. 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. # or the DNS query routing mechanisms used by most processes on # This file is not used by the host name and address resolution

also flushing the DNS cache was done but it didn't help sudo dscacheutil -flushcache.

flags: qr rd ra QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0ġ041 IN CNAME 38 IN CNAME 8794 IN CNAME e3191.c.Į3191.c. >HEADER<<- opcode: QUERY, status: NOERROR, id: 11298 $ dig > DiG 9.6.0-APPLE-P2 > (1 server found)

nslookup and dig both work fine $ nslookup 8.8.8.8Ĭanonical name = canonical name = canonical name = e3191.c.

PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes fromĪ guest user account was created, the DNS issue was still there when using

Can you ping those hosts? $ ping 8.8.8.8.

It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network. This error is most often caused by having no connection to the Internet or a misconfigured network. DNS is the network service that translates a website's name to its Internet address. The server at can't be found, because the DNS lookup failed. It doesn't work, see Google Chrome output:

Have you tried using 8.8.8.8 (google) or any of the OpenDNS.

I've also tried Google's 8.8.4.4 and 205.171.3.65 (which I found from GRC's DNS Benchmark to be the fastest). This is a company DNS server that is given with DHCP, it works well for What is/are the IP address(es) of the DNS(s) you want to use?.

Can you ping the DNS you want to use? $ ping.deleting connection credentials and adding it again.Things they've tried that have not worked: The computers are 15' MacBook Pros, early 2011 model. They can use DNS in a Windows 7 virtual machine (VMware Fusion 3.1.3) running under OS X. Some of my coworkers are having troubles on their Macs - DNS resolution does not work under Mac OS X.

Mac windows emulator dns issue