Add the New IP Segments (220.127.116.11/24, 18.104.22.168/24) to your whitelists – do not remove the existing IPs or net blocks you have whitelisted for Exostar.
Full Mesh FAQs
Should I change my company's firewalls to allow the entire segment or a specific address?
The nature of cloud services is that IP addresses may change. Exostar as been assigned dedicated IP ranges from which services may originate. To prevent any issues with IP addresses changing in the future your company should whitelist the entire range. The last octet (bit) of your IP address may not be the same as the current IP address's octet (bit) in the future.
Does this only affect the application or does this also affect the integration points that have been set up?
|Any application/integration point that uses the old IP address segments (22.214.171.124/23 & 126.96.36.199/24) will be given a new IP address in the new segments (188.8.131.52/24 & 184.108.40.206/24).|
Will Non-PROD (production) environment be changed before these PROD environments?
This project only is impacting the PROD (production) environments.
What actions/activities should we be focused on when validating that the change has no adverse effects? Are we expecting that we’ll need to do a complete application and integration regression test?
The functionality of the application is not being modified. Exostar is suggesting a smoke test and a flow of messages.
Does this IP address change have impact on API calls?
|If the API call is using one of the IPs in the Current segments, then this would impact the API calls. The API call user may have to restart the API service. If the API call uses DNS, then there should not be an issue.|
Is it mandatory for every business user to clear the cache/flush DNS?
It is not mandatory for every business user to clear the DNS cache. However, if the client DNS is handled properly once the Time-To-Live (TTL) expires, the record value should be refreshed with the new IP address. If that doesn’t occur users may have to flush (clear) cache.