Note: Avoid using NSLookup when you test the name resolution on the client. Doing a packet capture it doesnt look like the traffic even makes it to the DNS server.įunny enough nslookup will work, but I researched that it stated: When they try to ping internal DNS name, using the on prem Microsoft DNS server it just says "Ping request could not find host Please check the name and try again." In the browser it will say they recieved a NXDOMAIN response. ![]() (They can ping internal resources by IP only). Basically regular internet resolution works and the tunnel actually still stays active. We have a handful of users who lose their split-dns functionality after they are connected to the VPN for awhile. I've heard of this issue popping up Pre-COVID but very rarely and a reboot always fixed it. With a Cisco TAC case open actively trying to get it resolved. ![]() ![]() I've been beating myself trying to figure this issue out for weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |