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


Click here to return to the '10.3: Strange DNS behavior and workaround' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Strange DNS behavior and workaround
Authored by: clownburner on Dec 11, '03 08:21:35PM

Yes, that works to clear lookupd's cache, but doesn't change the fact that Panther is not following the standard practice (or the Jaguar method) for DNS lookups...



[ Reply to This | # ]
10.3: Strange DNS behavior and workaround
Authored by: vogunaescht on Dec 16, '03 03:55:26AM

True. Is there a proxy involved that might cache DNS entries? Another possibility is to run bind locally as a caching-only nameserver.



[ Reply to This | # ]
10.3: Strange DNS behavior and workaround
Authored by: DavidMaxWaterman on Jan 08, '04 02:01:40AM

We run our local domain in a similar manner to the original poster, and we have a local dns server to resolve local names.

I am the only one using a Mac and I am the only one that has problems using our dns server. The problem I see is that my initial attempts to load a web page fail; the second and subsequent attempts fail. If I don't visit that page for a while, the failure happens again, again only for the first attempt.

I used tethereal on the server to compare requests made by my Mac with requests made from other OSes (w2k and xp); the traces are here :

http://reality.sgiweb.org/maxw/tmp/Apple/3519742/

if anyone cares to look. To summarise, Mac makes this sort of sequence of requests :

http://reality.sgiweb.org/maxw/tmp/Apple/3519742/eth1-214-OSX-02-dns.txt

1 0.000000 192.168.0.214 -> 192.168.0.1 DNS Standard query A news.google.com
5 0.705145 192.168.0.214 -> 192.168.0.1 DNS Standard query A news.google.com
9 1.410272 192.168.0.214 -> 192.168.0.1 DNS Standard query A news.google.com
12 2.115540 192.168.0.214 -> 192.168.0.1 DNS Standard query A news.google.com.jingmei.org

It tries the 'news.google.com.jingmei.org; domain before the server has even responded to the first request.

I filed a bug (3519742) with Apple on this, but it does not seem to be getting any attention :( It's really messing me up; and is embarressing when all the various Microsoft OSes work fine.

Max.



[ Reply to This | # ]