Misconfigured DNS with Z3 and Inseego FX2000

[TODD BEERS]

We keep getting a misconfigured DNS error when using an Inseego FX2000 5G mifi from T-Mobile with Z3's, but not with MX64, MX64W or MX67. I've used 16.16, 16.16.6 and 18.10 firmware with same results. Hoping someone might have some experience with the FX2000 that could let us know what to tweak, whether that be Z3 or Inseego. Thanks!

[Raphael_L]

Hi ,

I don't have any Z3 to this , but is it affecting ALL your Z3s ?

If not , can you take a packet capture and see if the DNS requests sourced by the Z3 are received a valid response ?

If you are sure that everything is fine , I would suggest you to open a case with Meraki so that they can log this issue.

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications/Common_Dashboard_Alerts_for_Device_Connectivity#:~:text=DNS%20is%20Misconfigured,-As%20with%20almost&text=If%20there%20are%20no%20firewall,resolve....

Section : DNS is Misconfigured

[TODD BEERS]

Actually had it happen with a MX67 yesterday. Then it got stranger. I had network, but no Internet. Everything was getting resolved by internal DNS, but couldn't get out. I still have more testing to do. There's an option for passthrough IP on the Inseego. We'll see how that works.

[TODD BEERS · Accepted solution]

I think we've got it. We had to do manual DNS on the Inseego FX2000. Set it to Google (8.8.8.8) and let it marinate overnight. All good this morning. Rebooted the Inseegos - came back OK. Rebooted 2 test Z3's and a MX67 - Also came back good. So, the solution for DNS Misconfigured error is set the manual DNS on the Inseego.