[Big Mac]

I know this actually belongs in networking, but it's a general OS X issue, too; I need help ASAP. I have been bitten by the DNS cache problem that has plagued various users since the earliest versions of the OS. There is an essential domain that I need to access reliably that recently changed IPs. My iBook is on the same LAN as my G5, and it accesses the site with no problems. But my G5 insists on retaining the old lookup for some reason. I have tried lookupd -flushcache and kill lookupd -1 to no avail. On my iBook I am running 10.3.7, while on my G5 I am running 10.3.5; since I have a DP 2.0 my reasons for not updating to 10.3.8 are obvious. Is there anything else that I should try before giving up and performing an Archive and Install?

[JLL]

From what browser? I have had i similar issue where resetting Safari helped.

[Big Mac]

This is a system wide issue: across all browsers and users.

[Big Mac]

Okay, I figured it out! Flushing the cache (lookupd -flushcache) did nothing, and neither did killing lookupd - all that accomplished was to log me out and back in. But the dig command is what did it! So if you ever have a problem with DNS cache validity that you cannot solve with the other methods, use dig. All I needed to do was:

dig <IP address> <domain name>

I then tried to get to the site anyway and thankfully it resolved. Thank goodness! Thank you to the previous poster who wrote months (years?) ago on the forum concerning the dig command. Now, can anyone explain to me why/how this worked whereas the other methods failed?