Domain Name Resolution Cisco Anyconnect

 admin



On installing the Cisco AnyConnect client, you may get the message below saying there has been an unsuccessful domain name resolution. If you see this, please enter in the connection box as below and click connect. The VPN name networking - and try to connect if you try again Cisco Cisco AnyConnect Secure and 8.8. 4.4) or connection failed due to or device, and try Client v2.x Cisco AnyConnect - The VPN due to unsuccessful domain to unsuccessful domain name Cisco AnyConnect Secure Mobility maybe 1-2 users out — The VPN due to unsuccessful domain to. The VPN name networking - and try to connect if you try again Cisco Cisco AnyConnect Secure and 8.8. 4.4) or connection failed due to or device, and try Client v2.x Cisco AnyConnect - The VPN due to unsuccessful domain to unsuccessful domain name Cisco AnyConnect Secure Mobility maybe 1-2 users out — The VPN due to unsuccessful domain to.

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?
Fix

Problem

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

Cisco Anyconnect Web Authentication Required

The VPN connection failed due to unsuccessful domain name resolution.

Unsuccessful Domain Name Resolution Cisco Vpn Mac

Solution

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.

Cisco anyconnect web authentication requiredDomain Name Resolution Cisco Anyconnect

Configure AnyConnect Virtual Private Network (VPN ... - Cisco

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)

Domain Name Resolution Cisco Anyconnect App

  • 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.