Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Severe 10.5.2 DNS problems

Severe 10.5.2 DNS problems
Thread Tools
Posting Junkie
Join Date: Nov 2000
Location: in front of my Mac
Status: Offline
Reply With Quote
Mar 6, 2008, 01:24 PM
 
So the other day at the office I noticed that opening web pages suddenly took so long. I switched over to FF and it felt exactly the same. I then noticed that opening up ssh connections to remote machines took forever too. Back at home on my wireless network I had no troubles at all. The next day at work I swapped Ethernet cables, the switch, etc. and nothing changed.

I then figured it might be the DNS since that is (apart from the interface) the only difference between my office and home network connection. So I replace the two DNS entries I get from our DNS server here at work with two entries from OpenDNS.com: 208.67.222.222, 208.67.220.220. Bam, problem gone.

So what's the deal with these DNS troubles? Before 10.5.2 I had no such problems at all. And now all of the sudden and for no obvious reason Leopard doesn't want to play nice with the DNS server anymore? Does this sound familiar to anyone here?

In principle the problem is solved, but the solution isn't especially nice. OS X should work with the DNS server the DHCP server points to w/o the user manually entering another service. And of course regardless if the workaround works or not, I'd like to know what's going on. Any ideas?
     
Moderator
Join Date: Dec 2000
Location: Polwaristan
Status: Offline
Reply With Quote
Mar 6, 2008, 02:43 PM
 
Maybe your dns cache got messed up. Try flushing it.

In Terminal, type 'dscacheutil -flushcache' then press Enter. No quotes on the commands.
     
Simon  (op)
Posting Junkie
Join Date: Nov 2000
Location: in front of my Mac
Status: Offline
Reply With Quote
Mar 6, 2008, 03:37 PM
 
I forget to mention that. That was actually the very first thing I tried once I noticed that it was system-wide and not just Safari. Unfortunately no dice.
     
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status: Offline
Reply With Quote
Mar 6, 2008, 03:53 PM
 
Check on another machine at work. Maybe there's something wrong with the DNS servers your company is using and not your settings on your machine.

Steve
Celebrating 10 years and 4000 posts on MacNN!
     
Simon  (op)
Posting Junkie
Join Date: Nov 2000
Location: in front of my Mac
Status: Offline
Reply With Quote
Mar 7, 2008, 06:08 AM
 
I was wondering about that too. But nobody else was having these issues. So I figured out it must be my MBP.
     
Fresh-Faced Recruit
Join Date: May 2008
Status: Offline
Reply With Quote
May 27, 2008, 10:16 AM
 
Well, I had exact prob. here. After a call to my ISP they changed my DNS and the problem was solved, so I feel like there may be a incompatibility between the DNS server software and OS X 10.5.2!
Regards.
M.Zografski
     
Mac Elite
Join Date: Jul 2002
Status: Offline
Reply With Quote
May 27, 2008, 04:39 PM
 
DNS server quirks + Leopard DNS resolution quirks perhaps. OpenDNS must be good enough to overcome whatever issue Leopard has internally.
     
Moderator
Join Date: Dec 2000
Location: Polwaristan
Status: Offline
Reply With Quote
May 27, 2008, 07:21 PM
 
OpenDNS is indeed awesome.
     
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status: Offline
Reply With Quote
May 27, 2008, 08:44 PM
 
Originally Posted by TINITUS View Post
Well, I had exact prob. here. After a call to my ISP they changed my DNS and the problem was solved, so I feel like there may be a incompatibility between the DNS server software and OS X 10.5.2!
Regards.
M.Zografski
No incompatibility; DNS servers just take the text of the URL and look up the appropriate Internet IP to go with it. DNS is so standard that any browser can use it. No, I think this is just an ISP issue that involved (oops!) forgetting to get all the customers updated with new DNS server addresses in a timely manner. I've had it happen to me with SWB/AT&T, and that's all it was.
Glenn -----
OTR/L, MOT, Tx
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 05:20 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2