You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the tunneler will flush dns on startup but it also needs to flush dns when any service changes happen affecting DNS such as when posture checks cause services to become unavailable, or available. If dns is not flushed cached when services appear, the cached results may cause problems.
The text was updated successfully, but these errors were encountered:
I have noticed that sometimes I get a DNS result with ZET that makes it look like the service is working when the service isn't actually available. I think this issue might address the confusion of the partial failure by causing DNS to fail faster when the service isn't available.
Right now the tunneler will flush dns on startup but it also needs to flush dns when any service changes happen affecting DNS such as when posture checks cause services to become unavailable, or available. If dns is not flushed cached when services appear, the cached results may cause problems.
The text was updated successfully, but these errors were encountered: