My Chrome browser keep getting a DNS_PROBE_FINISHED_NXDOMAIN error when trying to get to asinzen.com

My Chrome browser keep getting a DNS_PROBE_FINISHED_NXDOMAIN error when trying to get to asinzen.com

If your chrome browser is unable to run AZInsight or getting a page saying DNS_PROBE_FINISHED_NXDOMAIN. This indicates that the browser is having issues using your DNS to resolve the asinzen domain. 

Possible solutions include

  • Power down your internet modem and router to allow them to fetch new DNS server entries from your internet provider
  • Hard code your chrome browser to use the 1.1.1.1 DNS settings 
  • Hard code your router or computer to use 8.8.8.8 or 8.4.4.4 or 1.1.1.1 DNS settings 
    • Related Articles

    • ERROR: 110

      ERROR-110 indicates that your Amazon store is already connected to an asinzen account. Issue Cause Your Amazon account is already connected to a different asinzen account. You can't use the same Amazon store on a different AZInsight subscription.
    • ERROR: 502

      ERROR-502 indicates the asinzen webserver encountered an issue processing your request. When this happens please contact support. Error code location: new user signup form
    • ERROR: 704

      ERROR 704 indicates that the extension is having trouble finding information on an specific product or category, most likely due to Amazon being set on another language other than english. To fix this issue, you just need to make sure that Amazon is ...
    • How to update Chrome extensions

      It's crucial to keep all your Chrome extensions, including AZInsight, up-to-date for optimal functionality. However, automatic updates can sometimes take up to 5 hours or not run at all. Don't worry, there's a solution! To ensure that you have the ...
    • Troubleshooting connection issues between your browser and the asinzen servers

      Use the troubleshooting table below to troubleshoot connection issues  Symptoms Possible Cause   Solution  Support images When clicking the login button you get an error "Something went wrong contact support"  Your firewall is blocking outbound or ...