Java Ignoring TTL in DNS?

We have an application in production that is running on a recent 1.5 JDK on Linux that recently ran into a problem with DNS. A 3rd party solution provider redesigned their network resulting in an IP address change for a server we were using in the application. Their TTL (Time To Live) for the record was 24 hours so I fully expected the change to take place without incident and put no further thought to it. Now, over a week later, I find out that our application is still connecting to the old IP address.

So, is Java ignoring TTLs in their DNS caching implementation? The underlying OS had the right information so it has to have something to do with Java. Whatever it is, I just had to take the system offline for 5 minutes to get new DNS information.