Our services have been running fine for several months; but now we are seeing this intermittent error a LOT.
We're on AWS and are being told to clear our DNS cache; but we have a multi-tenant solution and most of them are not having any issues. Some are seeing this error 100 times a day (10% of their transactions.)
Any suggestions?
Looks like the AWS AMI keeps the DNS cached entries for 8 hours or so.
Hi Mike,
Are you still having issues with this? If a customer is still having issues, it may be because a DNS server in their environment is not respecting the TTL values on the SOA/NS records. Fixing the current lack of connectivity is accomplished by clearing the DNS cache on the DNS server that is holding on to the bad value.
Hi Mike,
Are you still having issues with this? If a customer is still having issues, it may be because a DNS server in their environment is not respecting the TTL values on the SOA/NS records. Fixing the current lack of connectivity is accomplished by clearing the DNS cache on the DNS server that is holding on to the bad value.