This seems to be a problem with the JVM, but since I only run into it in long running programs like Tomcat, I'm asking here -- it seems that in an JSP, if I'm using URLConnection to retrieve a remote webpage, the IP address that is obtained when doing the lookup in URLConnection persists for the life of Tomcat/JVM even past the ttl for that record. For example:
- www.foo.com resolves to 1.2.3.4 with a ttl of 15 minutes - 30 minutes later, if I look up www.foo.com, it's still 1.2.3.4 though in the meantime I've updated it to 4.5.6.7 Is there a way to force the JVM internal DNS cache to be flushed? Thanks, Adi -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
