New To Mac-Forums?

Welcome to our community! Join the discussion today by registering your FREE account. If you have any problems with the registration process, please contact us!

Get your questions answered by community gurus Advice and insight from world-class Apple enthusiasts Exclusive access to members-only contests, giveaways and deals

Join today!

 
Start a Discussion
 

Mac-Forums Brief

Subscribe to Mac-Forums Brief to receive special offers from Mac-Forums partners and sponsors

Join the conversation RSS
OS X - Operating System General OS operation information and support

OS 10.6 - Snow Leopard keeps dropping DNS


Post Reply New Thread Subscribe

 
Thread Tools
bbell2000

 
Member Since: Jun 08, 2009
Location: Henniker, NH
Posts: 6
bbell2000 is on a distinguished road
Mac Specs: MBP (4,1) 2.5 GHz 4 GB 300GB OS X 10.5.6

bbell2000 is offline
I upgraded my iMac rev 5,1 from 10.5. The 10.6 install was flawless, but I lost name resolution for machines on my local network. I could ping Google, but could only ping local machines by IP address.

I went into my network settings and futzed around (changed IPv4 from DHCP to manual, then back to DHCP) and name resolution started working.

After a couple of hours, it stopped working again. Took the same steps mentioned above and it's working again.

Does anyone have any ideas as to how I might resolve this?
QUOTE Thanks
chscag

 
chscag's Avatar
 
Member Since: Jan 23, 2008
Location: Fort Worth, Texas
Posts: 39,648
chscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond reputechscag has a reputation beyond repute
Mac Specs: 27" iMac i5, 3.2 GHz, iPad 3, iPhone 5c, 3 iPods, OS X Mavericks

chscag is offline
Try resetting your router. Some folks have reported intermittent problems connecting after a Snow Leopard install. Resetting the router seems to have solved the problem for most.

Regards.
QUOTE Thanks
smbt

 
Member Since: Aug 29, 2009
Location: South Wales
Posts: 1
smbt is on a distinguished road
Mac Specs: Mac Pro 2.8GHz Quad core xeons, 8GB/Mac Book Pro/iMac

smbt is offline
I've also got this problem after upgrading my 3 Macs. Resetting the router has not solved it.

Connecting to my 2 Linux boxes in the Finder is as quick as it was under leopard but trying to connect to, or share the screen on the other Macs now takes about 2-3 mins.

There appears to be no DNS problems when running Win2008 server in Fusion!

Regards
QUOTE Thanks
bbell2000

 
Member Since: Jun 08, 2009
Location: Henniker, NH
Posts: 6
bbell2000 is on a distinguished road
Mac Specs: MBP (4,1) 2.5 GHz 4 GB 300GB OS X 10.5.6

bbell2000 is offline
Quote:
Originally Posted by chscag View Post
Try resetting your router. Some folks have reported intermittent problems connecting after a Snow Leopard install. Resetting the router seems to have solved the problem for most.

Regards.
The problem seems to have cleared by itself. My *router* is an Ubuntu server. My iMac uses the Ubuntu server for its primary DNS and my firewall (ipCop) as its secondary. If the problem comes up again, I reboot both and report back.

Thanks for the suggestion.
QUOTE Thanks
deong

 
Member Since: Aug 30, 2009
Posts: 1
deong is on a distinguished road

deong is offline
I'm running the same setup; I have a Linux DNS server that serves out internal IP addresses for my own domains, and I have my wireless router configured to broadcast that as the primary DNS server, and my ISP-supplied DSL router as the secondary server.

Under Snow Leopard, almost universally, requests to my domains would end up getting the external IP address rather than the internal one. I deleted the secondary DNS server from my wireless router configuration, so that my Snow Leopard machines only get one DNS server supplied, the internal one. That fixed the problem, but it would be nice to be able to configure my backup DNS server again.
QUOTE Thanks
monolithic.mike

 
Member Since: Sep 04, 2009
Posts: 1
monolithic.mike is on a distinguished road

monolithic.mike is offline
I am having the same problem. I upgraded my MacPro and my MacBook and they are both the same. My Primary internal dns is run off a xServe and secondary is my Smoothwall Firewall. I have restarted both, and the issue remains.
QUOTE Thanks
bbell2000

 
Member Since: Jun 08, 2009
Location: Henniker, NH
Posts: 6
bbell2000 is on a distinguished road
Mac Specs: MBP (4,1) 2.5 GHz 4 GB 300GB OS X 10.5.6

bbell2000 is offline
Reporting back...

After resetting my network settings for a second time on the iMac, it hasn't dropped DNS for 6 days now. Not sure why it took two tries, but it seems to be working.

Upgrading my MBP to Snow Leopard this weekend and will report back whether I have the same issues.
QUOTE Thanks
dtravis7

 
dtravis7's Avatar
 
Member Since: Jan 04, 2005
Location: Modesto, Ca.
Posts: 27,629
dtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond reputedtravis7 has a reputation beyond repute
Mac Specs: iMac 2.4 C2D 10.9.4, iMac 2.16 C2d 10.6.8, Macbook2007 10.8.4, Mac Mini 10.8.4, iPhone 3GS Note 8!!

dtravis7 is offline
Quote:
Originally Posted by smbt View Post
I've also got this problem after upgrading my 3 Macs. Resetting the router has not solved it.

Connecting to my 2 Linux boxes in the Finder is as quick as it was under leopard but trying to connect to, or share the screen on the other Macs now takes about 2-3 mins.

There appears to be no DNS problems when running Win2008 server in Fusion!

Regards
It takes my mac with Snow Leopard more like 2-3 seconds to share the screen here. That is with many other macs on the network and many PC's also. All connect very fast.
QUOTE Thanks
JohnDCCIU

 
Member Since: Nov 30, 2008
Posts: 1
JohnDCCIU is on a distinguished road

JohnDCCIU is offline
I've seen this broken DNS situation on a number of machines upgraded to SL, on various kinds of home and corporate-style networks. It's definitely a bug in SL.

The symptom that I see is simply that a dig will work on a DNS name just fine, returning the proper IP address. However any other command that uses the DNS name (curl, ping, any GUI app like Safari, etc) will claim that the DNS name won't resolve. Obviously bogus and a bug.

I tried various things, including dscacheutil -flushcache, fooling with the network settings, Locations, etc, and some would provide a temporary workaround, usually with some disruption.

However, I happened across a Parallels support topic that provided what seems like a sure-fire workaround, either temporary or longer-lasting, until Apple fixes this bug.

The basic workaround is to issue the command sudo killall mDNSResponder at the Terminal prompt when this issue occurs, and all starts working properly.

The Parallels support article has steps to make it a permanent workaround if desired, until Apple fixes it: KB Parallels: Cannot resolve DNS names inside Mac OS X Snow Leopard Guest
QUOTE Thanks
lsusparks

 
Member Since: Sep 09, 2009
Posts: 1
lsusparks is on a distinguished road

lsusparks is offline
I noticed this same exact problem on my MacPro yesterday. It was never an issue before 10.6. Changing the ttl on the DNS server fixed it for me (not much help if you don't have access to do that).

Here's the deal - one of our networks at work had ttl's of 5256000 seconds. I had trouble browsing to web servers on that network. Most other addresses worked fine, but had much lower ttl's. I asked our DNS administrator to adjust the ttl on one problem address down to 604800 and suddenly the problem is gone (for that one address). Then I had him change all records to be no more than 604800 (an arbitrary number on my part, 7 days vs 60 before). It seems totally fixed.

If you're seeing this on a home network, check if your router is doing dns caching or anything like that. If possible adjust the ttl or turn off the DNS caching and see if that fixes it.

To check if maybe this is your problem, use Network Utility to lookup the name. You'll see a line like this:
myserver.me.com 43200 IN A 10.10.10.15
That 43200 is the ttl (time to live, in seconds). I know from experience that 5256000 is too high an causes problems in SL, and that 604800 does work. Where exactly it breaks I'm not sure.

I'm interested to hear if this fixes anyone else's problems.
QUOTE Thanks
hphoto

 
Member Since: Sep 22, 2009
Posts: 2
hphoto is on a distinguished road

hphoto is offline
Quote:
Originally Posted by lsusparks View Post
I noticed this same exact problem on my MacPro yesterday. It was never an issue before 10.6. Changing the ttl on the DNS server fixed it for me (not much help if you don't have access to do that).

Here's the deal - one of our networks at work had ttl's of 5256000 seconds. I had trouble browsing to web servers on that network. Most other addresses worked fine, but had much lower ttl's. I asked our DNS administrator to adjust the ttl on one problem address down to 604800 and suddenly the problem is gone (for that one address). Then I had him change all records to be no more than 604800 (an arbitrary number on my part, 7 days vs 60 before). It seems totally fixed.

If you're seeing this on a home network, check if your router is doing dns caching or anything like that. If possible adjust the ttl or turn off the DNS caching and see if that fixes it.

To check if maybe this is your problem, use Network Utility to lookup the name. You'll see a line like this:
myserver.me.com 43200 IN A 10.10.10.15
That 43200 is the ttl (time to live, in seconds). I know from experience that 5256000 is too high an causes problems in SL, and that 604800 does work. Where exactly it breaks I'm not sure.

I'm interested to hear if this fixes anyone else's problems.
Thanks for the hint. Same problem with my Macbook Pro after upgrade. Aside from sleep, applications will not resolve local domain hostnames after a few minutes after boot. Disabling and renabling DHPC in Snow Leopard would cure this problem until a few minutes later and same problem occurs.

Seems like Snow Leopard is not respecting DNS ttl value of 0 by not querying the DNS server? I use DNSMasq (in a dd-wrt router) and that is the ttl default for local domain hostnames. Use "dig myhostname any" to confirm. I modified DNSMasq ttl to 1 second by adding this option:
local-ttl=1

and I no longer experience this problem. I hope this information can help someone.
QUOTE Thanks
hphoto

 
Member Since: Sep 22, 2009
Posts: 2
hphoto is on a distinguished road

hphoto is offline
Quote:
Originally Posted by hphoto View Post
Thanks for the hint. Same problem with my Macbook Pro after upgrade. Aside from sleep, applications will not resolve local domain hostnames after a few minutes after boot. Disabling and renabling DHPC in Snow Leopard would cure this problem until a few minutes later and same problem occurs.

Seems like Snow Leopard is not respecting DNS ttl value of 0 by not querying the DNS server? I use DNSMasq (in a dd-wrt router) and that is the ttl default for local domain hostnames. Use "dig myhostname any" to confirm. I modified DNSMasq ttl to 1 second by adding this option:
local-ttl=1

and I no longer experience this problem. I hope this information can help someone.

never mind. my MBP slept overnight, and the problem is occuring again. urgh! i should have never upgraded to Snow Leopard.
QUOTE Thanks
rnoser

 
Member Since: Dec 10, 2009
Posts: 1
rnoser is on a distinguished road

rnoser is offline
This was extremely frustrating for me as well. I have two Macs in the house, a Mini and MacBook. The Mini had no problems, but the MacBook I was about ready to toss out the window. I was able to fix it just a few days ago (waited to post just to make sure that it was indeed fixed).

My Setup:
My primary DNS is running BIND on a Fedora 11 box, and I'd previously had my internet router as a secondary DNS. Both being pushed out via DHCP from that same Fedora 11 box.

On a whim I removed the internet router as a secondary DNS, so that I only had my BIND DNS from the Fedora 11 box being pushed out via DHCP. That seems to have done the trick.

I don't know the ultimate root cause, or if this solution may work for anyone else, but figured I'd pass it along for anyone else that landed here.

Good luck!
QUOTE Thanks
Shrinky999

 
Member Since: Dec 15, 2009
Posts: 1
Shrinky999 is on a distinguished road

Shrinky999 is offline
Hi guys,

I'm having the same problems here on my 10.6.2 white Macbook, DNS stops working for my Airport card every now and then:
- it only happens for the Airport card (not the wired network card) => it's not a networking problem per se
- it happens shortly after waking, but can come back after "fixing" it at any time
- Disabling and reenabling the wireless card does help solving it (not permanently though)
- it happens when I use my router as DNS server as well as when I manually enter my ISP's, the OpenDNS or Google's DNS servers => it's not a problem with my router/home network
- connecting to a server based on the IP works like a charm => seems to be limited to DNS
- using dig (and the like) returns no result (timeout) => wtf?
- no other computer (Linux/Windows/iPhone) are affected

I thought about reinstalling SL, but then again I get the feeling that it isn't some sort of misconfiguration, but might be a bigger problem as so many of you guys are affected

Hope there's a fix for that soon!
Holger
QUOTE Thanks
panaman

 
Member Since: Dec 16, 2010
Posts: 1
panaman is on a distinguished road

panaman is offline
Quote:
Originally Posted by Shrinky999 View Post
Hi guys,

I'm having the same problems here on my 10.6.2 white Macbook, DNS stops working for my Airport card every now and then:
- it only happens for the Airport card (not the wired network card) => it's not a networking problem per se
- it happens shortly after waking, but can come back after "fixing" it at any time
- Disabling and reenabling the wireless card does help solving it (not permanently though)
- it happens when I use my router as DNS server as well as when I manually enter my ISP's, the OpenDNS or Google's DNS servers => it's not a problem with my router/home network
- connecting to a server based on the IP works like a charm => seems to be limited to DNS
- using dig (and the like) returns no result (timeout) => wtf?
- no other computer (Linux/Windows/iPhone) are affected

I thought about reinstalling SL, but then again I get the feeling that it isn't some sort of misconfiguration, but might be a bigger problem as so many of you guys are affected

Hope there's a fix for that soon!
Holger
Have you ever got fix to this problem, my wifes mac mini is exactly the same. It looses name resolution also. I can ping things by IP and stuff but no DNS lookups work. If I turn off the airport and then turn it back on it fixes the problem, but its only temporary.
QUOTE Thanks

Post Reply New Thread Subscribe


« Snow Leopard Install Issue | Powerbook G4 Question »
Thread Tools

Currently Active Users Viewing This Thread: 2 (0 members and 2 guests)
 
Posting 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 Off
Forum Jump

Similar Threads
Thread
Thread Starter
Forum
Replies
Last Post
Just did Snow Leopard clean installation stevegate OS X - Operating System 3 09-12-2009 10:13 PM
Leopard vs. snow leopard morganm OS X - Operating System 13 09-05-2009 09:57 AM
How to qualify for Snow Leopard Upgrade Mayahi OS X - Operating System 19 08-25-2009 01:54 PM
Should I get one now? or wait for Snow Leopard, with potential price drop? Zelnaga Apple Notebooks 9 08-07-2009 08:06 PM
Snow Leopard on new Macs? jcb815 OS X - Operating System 1 03-31-2009 01:09 PM

All times are GMT -4. The time now is 08:48 PM.

Powered by vBulletin
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
X

Welcome to Mac-Forums.com

Create your username to jump into the discussion!

New members like you have made this community the ultimate source for your Mac since 2003!


(4 digit year)

Already a member?