Troubleshooting DNS_PROBE_FINISHED_NXDOMAIN Error on VergeCloud

Troubleshooting DNS_PROBE_FINISHED_NXDOMAIN Error on VergeCloud

Understanding DNS_PROBE_FINISHED_NXDOMAIN Error

The DNS_PROBE_FINISHED_NXDOMAIN error occurs when a DNS lookup is performed for a domain name, but no corresponding IP address is found. NXDOMAIN stands for "Non-Existent Domain," indicating that the domain does not exist in the DNS system.

Causes of the Error

This error can result from various factors, such as:

  • Visitor-related issues: Local network or DNS problems on the visitor’s end.
  • Domain configuration issues: Problems with your DNS record settings.

Troubleshooting Steps

1. Check Domain Transfer Status

Ensure that your domain has been fully transferred to VergeCloud. The transfer process can take up to 24 hours. To confirm:

  • Use the DNS Checker tool to verify that VergeCloud’s nameservers (NS) are correctly configured for your domain.
  • Check that other DNS records (e.g., A or CNAME) are configured properly.

2. Verify DNS Records

If your domain is properly transferred, ensure that the DNS records point to the correct source IP address:

  • Log in to your VergeCloud panel and navigate to the DNS settings.
  • Review the A, CNAME, or other relevant records and confirm they are accurate.

3. Check for Domain/Subdomain Records

Within the VergeCloud panel, confirm that a valid DNS record exists for the domain or subdomain you are trying to use:

  • If no record exists, create one with the appropriate values (e.g., an A record for the root domain).
  • Ensure that the Cloud Icon is enabled for CDN acceleration, if applicable.

4. Examine Network Settings

Check the network settings of your device to rule out visitor-side issues:

  • Set a public DNS resolver, such as Google’s DNS (8.8.8.8).
  • Follow your operating system’s network documentation for guidance on configuring DNS settings.

Considerations

  • Propagation Time: After making changes to your DNS records, allow a few minutes for propagation to take effect.
  • Correct Nameserver Configuration: Ensure VergeCloud’s nameservers are properly set for your domain to function correctly.
  • Domain/Subdomain Records: Verify that all required DNS records for your domain or subdomains are present and accurate.
  • Public DNS Usage: Visitors encountering this error should consider using a public DNS, such as Google’s (8.8.8.8), to bypass local DNS resolution issues.

    • Related Articles

    • Troubleshooting ERR_SPDY_PROTOCOL_ERROR in Chrome

      What is ERR_SPDY_PROTOCOL_ERROR? The ERR_SPDY_PROTOCOL_ERROR occurs in Chrome when there is an issue with the SPDY or HTTP/2 protocol. This error can appear while trying to load a website, even for well-known domains. It typically stems from browser ...

    • Troubleshooting SSL Errors on VergeCloud CDN.

      Troubleshooting SSL Errors on VergeCloud If users encounter SSL errors while visiting your website and you are utilizing VergeCloud’s content delivery network (CDN), the issue may stem from several potential causes. This guide outlines common factors ...

    • Troubleshooting with cURL.

      cURL: An Essential Tool for Diagnostics What is cURL? cURL, short for Client for URLs, is a command-line tool used for transferring data over various protocols. It supports a broad array of devices and can be employed to test several scenarios, such ...

    • Troubleshooting Traffic Routing Through VergeCloud CDN

      After updating your NS records to utilize VergeCloud CDN, you might notice that the traffic isn’t yet routed through VergeCloud. This issue can arise due to two main reasons: Reason 1: Delay in Propagation of Changes Although you have updated your NS ...

    • Troubleshooting With Active CDN and Enabled Cloud Icon.

      Testing Main Server Connection With Active CDN When VergeCloud's CDN is enabled, the cloud icon in your user panel indicates that your website's main server address is masked behind VergeCloud's servers. Tools like ping and traceroute will return ...