@Inderdeep: for the setup you have made, which I believe is the non-meraki site2site vpn, all ipsec details will be coming from the Viptela side and that would limit the IPs that the Meraki can learned from the Viptela routes. Will you be able to share the setup or diagram? ... View more

We have the similar issue. However, we are able to ping and traceroute the DNS server. IP were statically configured, including the HQ DNS server, on the PC behind the MX remote branch. We tried as well to nslookup their internal IP and it is working plus able to access internal applications, but PC cannot communicate to the internet. Using a public DNS, we are still able connect to internet but cannot access their internal applications, though DNS server is reachable using ping and traceroute. ... View more