FireboxCloud at Azure issue with IKEv2 and DNS?
Hi
We have a FireboxCloud at Azure.
I have setup IKEv2 and i can fine connect to it.
I can ping internal and external resources by IP.
But i cant get DNS lookups working.
I haved set it to assign DNS server 8.8.8.8, and also did try with internal, but DNS resolving dosent work.
Could it be Azure dropping the UDP packets for DNS at some way?
0
Sign In to comment.
Comments
Hi @SimonRIT
Make sure that your windows PC isn't running a version of Windows that has an issue with IKEv2:
https://techsearch.watchguard.com/KB?type=Known Issues&SFDCID=kA16S000000SO0eSAG&lang=en_US
-James Carson
WatchGuard Customer Support
That IKEv2 issue with Windows 10 (and 11) causes the IKEv2 VPN to not even connect at all (yes we had machines with that issue, since patched).
At a guess, need to make sure that the Azure NSG side of things allows outbound traffic to the Internet as well.
I had a similar issue with a Firebox Cloud appliance where somebody else had set it up for me (we terminate site to site VPNs on it), however they didn't explicitly allow outbound Internet access for it so it kept throwing errors when trying to do updates etc.
Once that was done it worked perfectly.
May i ask, can one setup a trial for Firebox cloud?
There is a 30 day trial for the Azure Firebox Cloud in the Hourly / Pay As You Go (PAYG) option, shown here:
Firebox Cloud License Options
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/firebox_cloud/fb_cloud_licensing.html