Currently Being ModeratedNov 27, 2012 1:27 PM (in response to TeamHCN)
Does the same happen if you put manually your ISP's DNSs into the network card configuration?
In fact what do you have in your DNS settings for the network interface you use your static IP on?
Currently Being ModeratedNov 27, 2012 1:30 PM (in response to TeamHCN)
also I've just notice the date on some of the logs are from May 2011.
Misconfigured Time/Date on either the router or the computer may cause such and more issues.
Can you double check the date/time on your computer and router - so we can get it out of the way.
Currently Being ModeratedNov 27, 2012 1:35 PM (in response to tzbikowski)
All 3 computers' IP addresses are configured with DHCP via the router (each one has a manually assigned IP address, outside of the normal pool, using MAC address filtering), using Google DNS and google.com, google.ca in the DNS and searchdomains fields. The router timezone is set via ntp server, I've confirmed as of now that both it and the iMac are set correctly. The mdnsResponder entries at the end of the log might be old, but perhaps they show where/when my problems started? All of the other entries I posted are from the past 24 hours.
Currently Being ModeratedNov 27, 2012 1:38 PM (in response to TeamHCN)
So youuse google DNSs - fine. Those MUST be numbers not names.
Google DNSs are 184.108.40.206 and 220.127.116.11
can you confirm you have numbers not names in DNSs list?
Idealy if DNS list has only your router IP so your network can me managed centrally but public ones will work.
Currently Being ModeratedNov 28, 2012 10:44 AM (in response to tzbikowski)
Tzibowski, I hadn't thought of that before – sounds like a good time-saver. If I set my DNS in network preferences to my router IP, should I then set the search domain field to my router domain name?
In response to your question, yes, my DNS entries are IP addresses, not domain names. Still, I am convinced that mdnsResponder crashing is the cause of my problems. What I don't understand is why it crashes, why this happens on only 1 of my computers, and how prevent it from crashing in the future?
Currently Being ModeratedNov 28, 2012 2:52 PM (in response to TeamHCN)
Regarding search domains - those are not directly responsible for your internet conectivity.
You can read what they are here:
regarding the mdnsResponder
You can try dragging this file to the desktop & rebooting.
This should clear the issue.
Please let me know how it goes.
Currently Being ModeratedNov 30, 2012 2:31 PM (in response to tzbikowski)
I did as you suggested and rebooted, however now DNS fails to resolve at all. I've tried rebooting again, as well as undoing it by replacing the newly generated .plist with the original one and rebooting, but DNS resolution appears permanently DOA.
Currently Being ModeratedNov 30, 2012 5:03 PM (in response to TeamHCN)
I gave up hunting for a solution and backed up my HDD to an external. I did an erase-install of Snow Leopard, created a new user account and set up new networking preferences. So far, so good. I'm running the necessary software updates now, I'll test the network again after that's done. If all goes well I'll use Migration Assistant to restore my old user account and applications. Wish me luck
Currently Being ModeratedDec 3, 2012 3:36 PM (in response to tzbikowski)
I crossed my fingers about doing the reinstall; some user reports I found for 10.6.5 claimed mDNSResponder remained broken even after a fresh install. For me, under a fresh install of 10.6.8, the issue appears resolved.
Currently Being ModeratedMay 20, 2013 9:02 PM (in response to TeamHCN)
I'm somewhat new to mac os however I'm having this issue on my MBP. I have a mac mini hard wired and two wireless networks (one g & one n for streaming 1080p to xbmc to my phone & mbp). I am experiancing the same issues as you where DNS stops responding and the mDNSResponder reset only fixes the issue a part of the time.
When I boot camp into my windows partition & can connect to both networks with no issue so the problem does appear to be only with os x.
My question is when you did the re-install did you restore from a time machine backup? Reason I ask is that I'm assuming when you restore a time machine backup the network setting also get restored. I'm just wondering that if any files are corrupted they will get restored therefore briging the issue back?