---
title: Domain name service (DNS) caching
description: If needed, you can use two global configuration properties to control the caching of hostname-to-numeric IP address (DNS lookup) results returned from the name resolution services of the underlying operating system.
component: pingdirectory
version: 9.3
page_id: pingdirectory:pingdatametrics_server_administration_guide:pd_met_dns_caching
canonical_url: https://docs.pingidentity.com/pingdirectory/9.3/pingdatametrics_server_administration_guide/pd_met_dns_caching.html
revdate: September 13, 2023
---

# Domain name service (DNS) caching

If needed, you can use two global configuration properties to control the caching of hostname-to-numeric IP address (DNS lookup) results returned from the name resolution services of the underlying operating system.

Use the `dsconfig` tool to configure these properties:

* `network-address-cache-ttl`

  Sets the Java system property `networkaddress.cache.ttl`, and controls the length of time in seconds that a hostname-to-IP address mapping can be cached. The default behavior is to keep resolution results for one hour (3600 seconds). This setting applies to the server and all extensions loaded by the server.

* `network-address-outage-cache-enabled`

  Caches hostname-to-IP address results in the event of a DNS outage. This is set to `true` by default, meaning name resolution results are cached. Unexpected service interruptions can occur during planned or unplanned maintenance, network outages or an infrastructure attack. This cache can allow the server to function during a DNS outage with minimal impact. This cache is not available to server extensions.