DNS caching Behaviour for Internal Services on Netscaler.
Article ID: CTX209047
Updated On:
Description
DNS caching and Configuration issue.
Customer has a Netscaler gateway setup pointing to storefront and for the storefront customer has DNS A record configured for Storefront FQDN on netscaler .
When we remove DNS A record and then re add new DNS A record point to different IP Address ,still netscaler is resolving to old IP address that has been removed.
Resolution
This is an expected behavior .
Once you add a Storefront FDQN to Session profile/action on Netscaler Gateway as below ,
Once you add a Storefront FDQN to Session profile/action on Netscaler Gateway as below ,
DBS-service is actually created internally in the code,
Either we have to reduce the TTL or wait till the TTL gets over.
==>Netscaler will create a internal DBS Service for Storefront FQDN .The Old DNS Record will be flushed from DNS cache only after TTL is expired as this is an Internal DBS record not exposed to Netscaler config.Problem Cause
DNS Caching Behaviour on NetscalerIssue/Introduction
DNS Caching for Netscaler Gateway
Was this article helpful?
Yes
No
Powered by
