Nslookup/dig differ from how a browser resolves a hostname

domain-name-systemipnslookup

At my site, we just moved an important service, and made the appropriate DNS changes internally and externally to make it work.

When you bring up the site in a browser, it works fine. (Works in Safari, Chrome, Opera, Firefox, on computers that have been on the network for a while and ones that have been off it for some time.)

That's good, to be sure. But when I type nslookup <hostname> or dig <hostname>, I get the old IP for the service. (If I put said IP in the browser, I get the former server for this service).

I'm perplexed. How is it that the browser resolving the new service but nslookup is not? [No, there is nothing about the site in /etc/hosts].

[Incidentally, is there any way to tell which IP a browser came up with for a site?]

Best Answer

Another possibility is that the client machines on the network are going through an HTTP proxy server that picked up on the IP address change before they did.