DNS Issue when Client VPN connected

SOLVED
glm
Conversationalist

DNS Issue when Client VPN connected

We do not have DNS resolution when connected Client VPN. We have a MX250, firmware MX 14.40.  Our Client VPN configuration is the default "Use Google Public DNS".  When connected in our Client VPN subnet, ipconfig shows the DNS servers are as expected, 8.8.8.8 and 8.8.4.4. DNS resolution does not work (ping, RDP, browser, etc). My client device is Win10 19041.508. It had the issue with the prior Win10, 18363. What am I missing? Thank you.  -Greg

1 ACCEPTED SOLUTION
PhilipDAth
Kind of a big deal
Kind of a big deal

Have you got any firewall rules blocking the traffic?

View solution in original post

2 REPLIES 2
PhilipDAth
Kind of a big deal
Kind of a big deal

Have you got any firewall rules blocking the traffic?

glm
Conversationalist

Thank you for assist.  It was indeed a firewall rule. 

 

Since all of our other non-VPN subnets are assigned the gateway as their DNS server, a rule was never created for DNS egress, thus our final DENY rule was denying port 53 traffic from our Client VPN subnet.  Adding Outbound rules that allow port TCP and UDP 53 from our Client VPN subnet has allowed DNS resolution to Google's Public DNS to work.  Much appreciated!

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels