Test Kamo through a phone hotspot first; because reinstalling Kamo and trying Columbus, Indianapolis, and Chicago already failed, this test distinguishes a home-network DNS problem from a likely Kamo endpoint or service problem.
1. Test a different network
- Turn on the hotspot on a mobile phone.
- Connect the Windows 11 PC to that hotspot.
- Open Kamo and try one location once.
- If Kamo works: the DNS service or filtering on the normal network is likely preventing Kamo’s server names from resolving. Continue with the DNS change below.
- If the same error occurs: skip to If Kamo still fails across networks.
The error specifically means Windows or the application cannot translate the remote server name into an IP address.^1^
2. Test and refresh DNS
Open Start, type Command Prompt, select Run as administrator, and run:
nslookup example.com
ipconfig /flushdns
An nslookup result containing one or more addresses shows that general DNS resolution works. A timeout or “server failed” response indicates a broader DNS problem.
After flushing DNS, close and reopen Kamo and test again. Do not reinstall it again at this stage.
3. Temporarily use a public DNS resolver
If Kamo works on the hotspot—or nslookup fails on the normal network—change DNS on the active Wi-Fi or Ethernet adapter:
- Press Windows+R, enter
ncpa.cpl, and select OK. - Right-click the adapter currently providing Internet access—normally Wi-Fi or Ethernet—and select Properties.
- Select Internet Protocol Version 4 (TCP/IPv4), then Properties.
- Select Use the following DNS server addresses.
- Enter either:
- Cloudflare: preferred
[IP Address], alternate[IP Address] - Google: preferred
[IP Address], alternate[IP Address]
- Cloudflare: preferred
- Select OK, close the remaining windows, then run:
ipconfig /flushdns
Retry Kamo. If this does not help, return to the same IPv4 Properties window and select Obtain DNS server address automatically to restore the previous DHCP-controlled setting. DNS settings and the accuracy of the VPN server name are the primary checks for this error.^1^
4. Reset the Windows network stack
If DNS works but Kamo still fails, run these commands in an administrator Command Prompt, in order:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Restart Windows and test Kamo. Microsoft documents this sequence for resetting Winsock, TCP/IP, the assigned address, and the DNS resolver cache.^2^
If third-party antivirus, parental-control, “web shield,” secure-DNS, or router DNS-filtering software is installed, pause only the filtering feature you recognize, test Kamo once, and immediately re-enable it. Do not disable Windows security permanently. Firewall paths and the selected VPN protocol are standard VPN troubleshooting checks.^3^
5. Use Network reset only as a last resort
Go to:
Settings → Network & internet → Advanced network settings → Network reset → Reset now
This removes and reinstalls network adapters and restores their settings to defaults. It can also remove VPN adapters or settings, so Kamo might need to be set up again afterward.^2^
If Kamo still fails across networks
If the identical name-resolution error occurs on both the normal connection and a phone hotspot, with general nslookup working, that points more strongly to Kamo’s endpoint list or service-side DNS rather than a Windows-wide DNS failure. Use Help or Support inside Kamo, or the support option on Kamo’s official website, and provide:
- The complete error text
- Windows 11 version
- The three failed locations
- Whether the hotspot test also failed
- The date and approximate time of the attempts
Do not post an email address or other account information publicly.
References