| 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
You will see that Cisco Anyconnect displays an error message where it is not able to connect to the VPN host using the hostname. The first thing you will need to confirm is if the DNS resolution is working and in order to confirm that you will need to run the command prompt. Feb 16, 2015 Q: Cisco VPN - Connection failed unsuccessful domain name resolution. You are trying to connect to MIT's VPN, but get an error: The VPN connection failed due to unsuccessful domain name resolution. 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). Mar 17, 2021 If you received 'VPN connection failed due to unsuccessful domain name resolution' when using Cisco AnyConnect Secure Mobility Client, here's how to fix it.
You are trying to connect to MIT's VPN on vpn.mit.edu, but get an error:
Vpn Domain Name Resolution Error
The VPN connection failed due to unsuccessful domain name resolution.
Solution
Anyconnect Unsuccessful Domain Name Resolution
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)
- 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.
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.
Answer
First, make sure that the problem only affects the Cisco VPN. 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)
- 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.