Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Domain name server problems and long delays System
If for some reason the domain name servers (DNS) are not responding, but the network connection is up (for example, if the domain name servers are down), NetInfo takes ages to authenticate a user (probably because it tries to look up something and there is a long timeout delay).

The problem shows up, for example, when trying to de-activate the screensaver. The problem is made much worse by the fact that the screensaver seems to have a glitch which removes the password screen right after it is done showing the spinning ball for a few minutes, making it practically impossible to deactivate.

The solution is simple: unplug the network cable, and within a few seconds everything is back to normal. I do not know if Apple is aware of this bug.
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)

Domain name server problems and long delays | 18 comments | Create New Account
Click here to return to the 'Domain name server problems and long delays' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Another Solution
Authored by: riffraff on Jun 03, '02 11:04:18AM

Indeed, this problem has ticked me off on many occasions when my DSL has been down. If you don't feel like reaching around to pull your network cable from your computer, or if you'd have to go crawling under your desk to do so, you can effect the same temporary solution by going into the Network panel of your System Preferences. There is an option therein (forgive me for not being specific, I'm not at my computer, so I can't check out exactly where it is) to disable your network profiles. All you have to do is uncheck the affected profile, apply, and you should be okay 'til your connection comes back. When I have to do this, I generally minimize the Sys. Prefs. window to the dock so I can just pull it up and recheck the profile to test if it's working yet.

[ Reply to This | # ]
Authored by: sharumpe on Jun 03, '02 12:40:56PM

Of course, if you're using AirPort you can't do this - there's no way to unplug the network.

I have had this problem MANY times, and, for the most part, the only option is to either wait for an (unspecified) LONG time, or reboot. Neither is a good option, but sometimes time constraints force a reboot.

My favorite scenario would be a Linux-style multiple console setup, where you can hit alt-f1 or some key combo to get a text-based login. Then you would always be able to get in and do whatever is necessary (take down network, kill loginwindow process, etc.).

Mr. Sharumpe

[ Reply to This | # ]
AirPort can be turned off
Authored by: nagani on Jun 03, '02 01:06:10PM

If you have enabled 'Show Airport status un menu bar' in your Network preferences, there is a "Turn Airport Off" menu available when you click on the signal strength icon...

[ Reply to This | # ]
AirPort can be turned off
Authored by: Anonymous on Jun 03, '02 11:37:33PM

And remind us all how we turn AirPort off while the screensaver is on!?

[ Reply to This | # ]
Authored by: eagle_eyes on Jun 03, '02 02:06:18PM

I have a location set up in the network preferences that takes care of these very problems. All it has is every network type turned off. Very nice for solving problems

[ Reply to This | # ]
locations all off. How?
Authored by: MtnBiker on Jun 03, '02 02:20:21PM

What are the setting for nothing connected?

Leaving things blank? I don't see any off type choices.


[ Reply to This | # ]
locations all off. How?
Authored by: CaptCosmic on Jun 03, '02 02:51:01PM

Go to the Network Preferences pane. Create a new Location called Networkless (or something similar). Then, Click the Show drop down box, and choose Active Network Ports. This will give you a list of all of the Active Ports on the system. Simply uncheck all of the boxes in the list, and click apply. You now have a Location with no network.

It's great for those times when you don't have a wireless connection and don't want the airport draining the battery looking for one.

-> Capt Cosmic <-

[ Reply to This | # ]
Re: locations all off. How?
Authored by: sjk on Jun 03, '02 06:12:56PM

First time I tried this I was only able to uncheck Internal Modem; couldn't even select (i.e. highlight) any of the other active ports. I deleted/recreated the "No Network" entry, then couldn't uncheck or select *any* of the active ports. Toggling the changes lock didn't help. Weird.

[ Reply to This | # ]
dial-up airport == bad
Authored by: Desdicardo on Jun 03, '02 07:28:03PM

This is the most annoying problem I have encountered since I bought
my mac. I have a TiBook and an Airport base station. I can't get
broadband so I have the Airport set up to connect via dial-up. This
problem occurs whenever I am not dialed in; i.e. 80% of the time. I
have to religiously turn off the airport whenever I am not connected.
I find this rather ironic since I switched to wireless for the
convenience... its turned out to be anything but.

I am currently in the process of setting up a local FreeBSD gateway.
I'm hoping if I can run a local caching name server NetInfo will
behave itself.

[ Reply to This | # ]
dial-up airport == bad
Authored by: GreyArea on Jun 04, '02 04:29:44AM

I'm running a local FreeBSD box here and if you set it up as a caching DNS then it will indeed solve your NetInfo login problems. I'm personally running qdns.


[ Reply to This | # ]
dial-up airport == bad
Authored by: GreyArea on Jun 04, '02 06:33:36AM

Correction - I'm using 'pdnsd'. Don't ask me where I got qdns from...!


[ Reply to This | # ]
Still Another Solution
Authored by: razberry on Jun 03, '02 07:48:01PM

I find the name server problem a tad annoying myself. My solution involves using the terminal window and doing a few things as root.

do a 'ps -ax | fgrep lookupd'. You should see the lookupd daemon's process ID. Kill that daemon. Then type 'lookupd' to start it up again.

I'm sure someone can make a little shell/perl script (maybe even applescript) to do this for us.


[ Reply to This | # ]
Still Another Solution
Authored by: tarbosh on Jun 04, '02 11:48:19AM

You really shouldn't be arbitrarily killing lookupd. Bad things can happen. Instead, send it a hang up signal-

sudo kill -HUP `cat /private/var/run/`

your post does get to the root of the issue, however, which has not a thing to do with netinfo, and everyhting to do with lookupd.

[ Reply to This | # ]
The main issue here…
Authored by: Anonymous on Jun 03, '02 11:42:39PM

The main issue here though is why NetInfo requires access to name servers at all if the currently logged in user was authenticated against the local NetInfo database?

(Saying that, another way to get round the problem would presumably be to run a local name server and point System Prefs to that.)

[ Reply to This | # ]
The main issue here…
Authored by: tarbosh on Jun 04, '02 11:52:57AM

NetInfo does not. NetInfo is NOTHING but a place to store information. It is functionally equivilent to an excell spreadsheet, an oracle database, or a series of flat files.

All it does is supply information when requested. At no point does it do DNS lookups.

lookupd- specifically the resolver in lookupd- does that.

[ Reply to This | # ]
The main issue here…
Authored by: Anonymous on Jun 05, '02 07:54:05PM


[ Reply to This | # ]
NetInfo delay
Authored by: bryanzak on Jun 04, '02 09:54:38AM

This is was discussed extensively on Apple\\\'s darwin development mailing list. I believe it is fixed in Jaguar.

[ Reply to This | # ]
Long Logout
Authored by: mnewman on Jun 04, '02 07:11:34PM

I wonder if this is why my iBook can take so long to finish the logout process if I disconnect the Airport dial-up connection before logging out? If I leave the Aiport dialed-up the logout takes seconds, if not, it can take several minutes before the login screen appears.

[ Reply to This | # ]