search cancel

Connectivity has been lost (Target could not be resolved)

book

Article ID: 254010

calendar_today

Updated On:

Products

AppNeta

Issue/Introduction

An appliance is getting this error/alert almost every day, multiple times per day for one specific web path only:

"Connectivity has been lost (Target could not be resolved)"

Other appliances monitoring this web path do not have this issue.

Environment

Release : SAAS

Resolution

If an outage causes a route change, and one or more hops on the new route do not resolve correctly in DNS, then this error will be generated.

For example, if the target has two IP addresses and when the route changes between them, one of these gives you the problem. The primary route to target is resolving correctly via DNS while the secondary is not.

Check the route from the device to this target, ensure all ports are open and and that DNS resolve properly.