NetBeans seems to use a DNS cache separate from the O/S.  When developing web sites with my laptop in different locations, it would be really handy if I could get this cache flushed (one LAN IP address when at work, one EXTERNAL IP address from a local DNS server when at home).  Windows' own resolver has no problem with this CONCEPT and I can always run ipconfig /flushdns if needs be.  But NetBeans is still looking in the wrong place.

Does anyone know if there's any simple, non-programmatic way of flushing this cache?Just as an aside, when I tried again an hour or so later (in the new location), the DNS lookup was resolved afresh (correctly) so I presume the cached entry had HIT its TTL.  It's a nuisance!I found this:
http://www.rgagnon.com/javadetails/java-0445.html

Since NetBeans is written in Java (as far as I recall) it would be susceptible to this "feature" where the JVM has it's own cache of network addresses, which sounds like it could be the cause of your issue.Indeed, that's my understanding.  I'm not really up to the challenge of hacking the NetBeans code and recompiling to fix this "feature"...  I'm betting there is a way of flushing this cache - but is it private PER application though?  That seems inefficient, but who knows.Hang on - reading that article more closely, there's a suggestion a JRE setting might fix it.  I'll try that.  Thanks! Quote from: Rob Pomeroy on December 13, 2011, 01:56:01 PM

Hang on - reading that article more closely, there's a suggestion a JRE setting might fix it.  I'll try that.  Thanks!