A DESCRIPTION OF THE REQUEST :
Default value for property networkaddress.cache.ttl is -1 that means infinitive cacheing. Property must have lesser default value.
JUSTIFICATION :
Because Java must be more user friendly.
Now I have the situation when same address string resolved to different IPs in my home and in the office. It's normal situation, it does not violates any standards, and it is good practice. In fact, I just switch values in /etc/hosts.
I never turn off my notebook. So I have to restart my networked Java apps (my IDE and one other app) each time I came home from office, and when I came to office back.
I can edit this property somewhere in program preferences, or in JDK installation dir, but it is hard, and not user friendly. Java must be handy out of box.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Lesser value of networkaddress.cache.ttl. I think 1 minute is good.
ACTUAL -
networkaddress.cache.ttl: -1 (infinitive)
Default value for property networkaddress.cache.ttl is -1 that means infinitive cacheing. Property must have lesser default value.
JUSTIFICATION :
Because Java must be more user friendly.
Now I have the situation when same address string resolved to different IPs in my home and in the office. It's normal situation, it does not violates any standards, and it is good practice. In fact, I just switch values in /etc/hosts.
I never turn off my notebook. So I have to restart my networked Java apps (my IDE and one other app) each time I came home from office, and when I came to office back.
I can edit this property somewhere in program preferences, or in JDK installation dir, but it is hard, and not user friendly. Java must be handy out of box.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Lesser value of networkaddress.cache.ttl. I think 1 minute is good.
ACTUAL -
networkaddress.cache.ttl: -1 (infinitive)
- relates to
-
JDK-8274692 DNS cache might violate Internet Standards as defined per RFC 1035, 2181, 8767
-
- Open
-