Verid DNS Failover
3 years ago
Originally Published: 2012-03-28
Article Number
000061713
Issue

The client cannot connect to Verid

 


Cause
DNS Failover
Resolution
Typically when moving from primary to secondary site, we do so via load balancers.  In the rare instances, when we change from our priimary site to our secondary site via DNS and Clients are not set to follow DNS, the client will have to do one of two things.  If they are using Java for example, they will need to restart the Java service because Java cache's IP's and will not automatically go out and look for new ones unless service is restarted. 
If a client has hard coded IP's they will be required to physically change the IP's we are currently resolving to.

Related Articles

Trending Articles

Don't see what you're looking for?