When I change the IP address of a website, the URL monitor still pings the old IP.

When I change the IP address of a website, the URL monitor still pings the old IP.

Reason: 
    Upon successful DNS lookup, Applications Manager by default, caches the resolved IP forever. This IP might be used even if there is a change in IP address.

Solution:
    We should specify the amount of time a successful lookup should be cached. To do so, Please do the following : 
  1. Navigate to '<AppManagerHome>/working/jre/lib/security' and open the 'java.security' file present there.
  2. Search for the key 'networkaddress.cache.ttl'. By default, this key is commented. 
  3. Uncomment it and set the value to the number of seconds you wish to cache the successful lookup. A value of -1 indicates 'cache forever'.
  4. Restart Applications Manager and check if the issue is resolved. 

Still facing issues?
If the problem persists, contact our support team along with the following details:
  1. A screenshot of the "Add Monitor" page. 
  2. The URL debug tool response for the URL monitor.
  3. Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".

                  New to ADSelfService Plus?

                    • Related Articles

                    • Troubleshooting URL Monitor

                      When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...
                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...
                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...
                    • How to get ISP and Region data in Real User Monitor?

                      The default setting of the Real User Monitor does not display ISP and region data for the end user. To obtain the data, you have the option to use a third-party Geolocation API. Currently, RUM exclusively supports APIs that provide responses in JSON ...
                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...