not that it's much help either, but i experienced exactly the same thing when setting up a network for a friend...

a powermac g4 and a laptop running xp are both set up to access the internet through a third party wlan DHCP router (t-online crap).. the laptop manages without any promlems, the mac occasionally fails, but instantly manages to load the page on a second try... i tried new DNS servers, static or dynamic IPs and a lot of voodoo, to no avail...

also the g4 looses the connection on sleep-wake and only gets it back by changing settings, but that seems to be a widespread issue with airport.

++ christoph ++

Strange DNS lookup problems
 

I hoped to get something looking at lookupd. That's the responsable of resolving dns query, but it seems to have a timeout of 30 seconds:

skinner:~ root# lookupd -configuration
ConfigSource: default
LookupOrder: Cache NI DS
MaxIdleServers: 4
MaxIdleThreads: 2
MaxThreads: 64
TimeToLive: 43200
Timeout: 30
ValidateCache: YES
ValidationLatency: 15
_config_name: Global Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Host Configuration

LookupOrder: Cache FF NI DS
_config_name: Service Configuration

LookupOrder: Cache FF NI DS
_config_name: Protocol Configuration

LookupOrder: Cache FF NI DS
_config_name: Rpc Configuration

TimeToLive: 60
ValidateCache: NO
_config_name: Group Configuration

TimeToLive: 300
ValidateCache: NO
_config_name: Initgroup Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Network Configuration


It's possible to change the Timeout parameters (see man lookupd) creating a file /etc/lookupd/global with just a line:
Timeout 10

Then you have the kill the running process lookupd. It restart by itself.
Just look with lookupd -configuration to see if the parameter has changed.

Sorry I couldn't test it, since my network and dns now is fast.

Slow DNS lookups on Mac OS X
 

I've had this problem on several different macs in my soho net. It came down to being across a slow-ish bursty (Satellite IP) Internet connection.

Every first DNS lookup takes longer than one second. Then the response comes back, and if I try to reload the page a second time, it's gets the IP immediately and loads normally. While I could tolerate this behavior, it was annoying.

After reading this thread, I went and found /etc/resolver/local

$ cat /etc/resolver/local | grep timeout
timeout 1
$

I then edited the file and changed the timeout:
timeout 10

And now DNS lookups take a better pause to accomodate a slow WAN link on mac os x.

Slow DNS lookups on Mac OS X
 

I've tried to raise the timeout value in /etc/resolver/local, but it seems not to go better. Maybe I need more testing.

I've found another workaround. I duplicated the nameserver line in /etc/resolv.conf, so the query to dns is sent more than once.

domain pc.ibn
search srv.ibn pc.ibn
nameserver 192.168.0.2
nameserver 192.168.0.2
nameserver 192.168.0.2

With just one line the error answer come out after 2-3 seconds. With 2 lines the timeout become 5-6 seconds and so on.

Thanks, folks! That was the answer I've been looking for about changing the timeout value. Only I think the place to make the change would be:

/etc/lookupd/agents/DNSAgent/global

based on the lookupd man page. This file and much of that path don't exist in the default configuration. Also, the default value is supposedly 30 seconds, so setting a timeout value >30 would be the thing to try.

I believe the "/etc/resolver/local" mentioned above (with the 1 second timeout) is meant for Rendezvous lookups in the .local domain, so in general I wouldn't expect it to affect Internet lookups.


edit - I set a timeout value of 60, and restarted successfully. Since I haven't experienced much in the way of timeout troubles anyway, perhaps someone who is would be willing to try this?

It works for me with some modifications
 

I created /etc/lookupd/agents/DNSAgent and wrote a file called global in there that contains one line: Timeout 60

Here is my lookupd -configuration:
ConfigSource: file://etc/lookupd
LookupOrder: Cache NI DS
MaxIdleServers: 4
MaxIdleThreads: 2
MaxThreads: 64
TimeToLive: 43200
Timeout: 30
ValidateCache: YES
ValidationLatency: 15
_config_name: Global Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Host Configuration

LookupOrder: Cache FF NI DS
_config_name: Service Configuration

LookupOrder: Cache FF NI DS
_config_name: Protocol Configuration

LookupOrder: Cache FF NI DS
_config_name: Rpc Configuration

TimeToLive: 60
ValidateCache: NO
_config_name: Group Configuration

TimeToLive: 300
ValidateCache: NO
_config_name: Initgroup Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Network Configuration

Timeout: 60
_config_name: DNSAgent Configuration

As you can see from the last line, the new config is being read - but I still timeout on URL's that are not cached and even sometimes on known URL's that are experiencing some weird latency.

I tried putting a global file with the same contents at /etc/lookupd and my config looks like this:

ConfigSource: file://etc/lookupd
LookupOrder: Cache NI DS
MaxIdleServers: 4
MaxIdleThreads: 2
MaxThreads: 64
TimeToLive: 43200
Timeout: 60
ValidateCache: YES
ValidationLatency: 15
_config_name: Global Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Host Configuration

LookupOrder: Cache FF NI DS
_config_name: Service Configuration

LookupOrder: Cache FF NI DS
_config_name: Protocol Configuration

LookupOrder: Cache FF NI DS
_config_name: Rpc Configuration

TimeToLive: 60
ValidateCache: NO
_config_name: Group Configuration

TimeToLive: 300
ValidateCache: NO
_config_name: Initgroup Configuration

LookupOrder: Cache FF DNS NI DS
_config_name: Network Configuration

Timeout: 60
_config_name: DNSAgent Configuration

and it worked. So maybe that is a better path.?

**Just a note: my particular situation is that I am three hops away from my DNS server. When I am at home, where I am only one hop away I never have this issue.**

There was a hint that I have not been able to locate quickly, suggesting that IPv6 issues are responsible for the lookups taking so long. Several people have fixed the problem by disabling IPv6 in /etc/hostconfig. The hint refered to this page:
http://www.codepoetry.net/archives/2...bledip_dns.php. I have yet to reboot to see if it fixes the problem.

I am having the same problems using the middle click on my mouse to open new tabs, i hope they fix this soon.

http://docs.info.apple.com/article.html?artnum=106799
 

This is what I found on the Apple Website. http://docs.info.apple.com/article.html?artnum=106799

I changed the DNS server as specified (checked an windows machine to find the DNS servers). Since then I do not have internet issues anymore.

Interestingly, I just unplugged my ethernet connection to my netgear firewall/router and plugged ny G4 running 10.3.5 directly into my router and was able to access sites that were previously not reachable. So obviously the router and 10.3.5 are mixing well. Also, 10.3.7 apparently fixes this issue but at the loss of quartz extreme in older macs.