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


Click here to return to the 'A possible solution for failed DNS lookups on 10.3' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible solution for failed DNS lookups on 10.3
Authored by: kevin_stevens on Nov 12, '04 03:00:12AM

I only started having this problem recently - perhaps 10.3.5 or so. Just ran a tcpdump and noticed that my PowerBook was attempting to do a reverse lookup on the DNS server's IP address, attempting four times for each IP address request. Fortunately, I run my own DNS server, and correcting the reverse lookup record (which had become obsolete) fixed the reverse attempts. My reload problems went away immediately.

It's possible that the reverse lookup validation of the DNS server is a recent security-related change. If so, it could explain the varying results people are having. Just a data point.

KeS



[ Reply to This | # ]
A possible solution for failed DNS lookups on 10.3
Authored by: ngb on Nov 14, '04 06:09:41AM

This theory would seem to be supported by my own situation. I had not had the problem prior to applying the most recent security update (the one released prior to 10.3.6), but now am having this problem on about 30% of new sites, and even on some sites I have visited before. Using the router IP address for my DNS appears to have solved the problem.



[ Reply to This | # ]