Hey everyone, we're dealing with a puzzling issue for a new customer. They have a Meraki VPN set up, and they swear they haven't blocked any traffic from Azure, both incoming and outgoing via the VPN. We've configured a Site-to-Site (S2S) VPN on the Azure side and set up DNS forwarding rules for the clients, the usual steps you'd take. However, the customer isn't seeing any traffic on port 53, even though everything else seems to be working fine, like port 443. On our end, the firewall shows that traffic is allowed outbound for port 53. It's strange that port 53 is the only one not functioning as expected. Any thoughts on what could be causing this? We're starting to suspect it's a Meraki issue, but their support hasn't seen any evidence of port 53 being blocked either.
3 Answers
I've heard of Azure blocking certain ports, but blocking port 53 is pretty uncommon. Can you share a bit more about your routing setup and the components you're using on both sides? It might help narrow down the issue!
Because you've covered the basics, here’s a thought: Double-check your DNS settings and ensure all necessary ranges for on-prem DNS are included in your local gateway config. It's odd that every other service works except port 53. Have you tested the DNS forwarding rules carefully?
Yeah, it's a head-scratcher! Have you tried opening all other NSGs on your virtual networks temporarily? Sometimes, those settings can be a hidden culprit. And are you sure the right forwarding rules are pointed in the right direction?
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures