Anyconnect Unsuccessful Domain Name Resolution

admin



Resolution

VPN connection failed due to unsuccessful domain name resolution is a common error that may occur when using Cisco AnyConnect Secure Mobility Client. The Common Name (CN) in the Subject-Name should be configured with the IP address or Fully Qualified Domain Name (FQDN) which users use to connect to the AnyConnect gateway; in this example, the clients use the FQDN of fdenofa-SSLVPN.cisco.com when they attempt to connect. Xls to vcf for mac.

Skip to end of metadataGo to start of metadata
You are viewing an old version of this page. View the current version.Compare with Current | View Page History

Anyconnect Unsuccessful Domain Name Resolution Mean

Name

You are trying to connect to MIT's VPN, but get an error:

The VPN connection failed due to unsuccessful domain name resolution.

Answer

The cause is not fully known, but this is seen more frequently when people are using Google Public DNS (DNS servers 8.8.8.8 and 8.8.4.4)

  • Try using another DNS server, such as your ISP's DNS server
  • Try sending some pings to vpn.mit.edu before connecting; these can help cache the IP address in your DNS cache.
  • Wait a few minutes and try connecting again; the connection can work if you try again later.
Labels parameters
Labels:
None
This article refers to the Cisco AnyConnect VPN. If you're looking for information on the Prisma Access VPN Beta that uses the GobalConnect app, see: Prisma Access VPN Landing Page.
If you're not sure which service you're using, see: How do I know if I'm using the Cisco AnyConnect VPN or the Prisma Access VPN?

Problem

Anyconnect Unsuccessful Domain Name Resolution Program

You are trying to connect to MIT's VPN on vpn.mit.edu, but get an error:

The VPN connection failed due to unsuccessful domain name resolution.

Solution

Name

First, make sure that the problem only affects the Cisco VPN app. Test vpn.mit.edu with other tools such as a web browser, or 'ping' the hostname.

The cause is not fully known, but this is seen more frequently when people are using Google Public DNS (DNS servers 8.8.8.8 and 8.8.4.4)

Cisco Anyconnect Failed Unsuccessful Domain Name Resolution Mac

  • Try using another DNS server, such as your ISP's DNS server
  • Try sending some pings to vpn.mit.edu before connecting; these can help cache the IP address in your DNS cache.
  • Wait a few minutes and try connecting again; the connection can work if you try again later.