DNS cache in AM

[CharlesVonHagen]

At the AM or SUSE Linux layer is there any DNS caching to deliberately extend the minimum TTL for a zone file entry? 

SMSDelivery
Functional Specification   question 7.1

The application framework (Java, .NET, etc.) layer, which by default typically caches DNS lookups.

The OS/Machine layer. This is uncommon but should still be verified

These questions came from our SMS provider Authentify to ensure that if they have maintenance and need to swing all ODA traffic to another data center, we don’t experience an outage due to our deliberate extension of DNS cached answers.

Thanks Chuck

[EdwardDavis · Accepted solution]

In AM, DNS lookups being cached... it is java.security setting. We do not recommend changes to this file.

/opt/rsa/am/appserver/jdk/jre/lib/security/java.security

8.4.0.11.0 uses defaults which is 30 seconds for positive lookups.

We do not set forever (-1) so 30 seconds is the result.

#
# The Java-level namelookup cache policy for successful lookups:
#
# any negative value: caching forever
# any positive value: the number of seconds to cache an address for
# zero: do not cache
#
# default value is forever (FOREVER). For security reasons, this
# caching is made forever when a security manager is set. When a security
# manager is not set, the default behavior in this implementation
# is to cache for 30 seconds.

# networkaddress.cache.ttl=-1