Google Cloud静态网站搭建后出现DNS_PROBE_FINISHED_NXDOMAIN错误求助

Since your server IP (34.120.167.35) is still accessible directly, the root issue is domain name resolution failure—not your static website setup. Let’s walk through actionable checks to narrow this down:

1. Verify DNS Record Existence & Correctness #

First, confirm your A record is still present and properly configured in BlueHost’s DNS panel:

• Log into BlueHost, navigate to your domain’s DNS management section.
• Check for an A record pointing lihenghenrychang.com (and optionally www.lihenghenrychang.com) to 34.120.167.35. Ensure it wasn’t accidentally deleted, modified, or overwritten (e.g., by a conflicting CNAME record).
• Note the TTL (Time To Live) value—if it was set to a high number (like 86400 seconds/24 hours), old cached records might still be in play, but a full day should be enough for most caches to refresh.

2. Test DNS Resolution Manually #

Use command-line tools to bypass local ISP caches and check what global DNS servers see:

• On macOS/Linux: Run dig lihenghenrychang.com A or nslookup lihenghenrychang.com 8.8.8.8 (using Google’s public DNS).
• On Windows: Open Command Prompt and run nslookup lihenghenrychang.com 8.8.8.8 or tracert -d lihenghenrychang.com.
• If these commands return NXDOMAIN, it means BlueHost’s DNS servers aren’t serving your A record at all—this points to a problem with BlueHost’s DNS configuration, not Google.

3. Rule Out Local & ISP Cache Issues #

• Flush local DNS cache:
  • Windows: ipconfig /flushdns
  • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Linux (systemd): sudo systemd-resolve --flush-caches
• Try accessing the domain from a different network (e.g., mobile data instead of home WiFi) to rule out your ISP’s cached records.

4. Check Domain & SSL Validation Status #

• Confirm your domain is active: In BlueHost’s domain manager, check that lihenghenrychang.com isn’t expired, locked, or in a pending transfer state.
• Verify Google SSL validation records: Ensure the TXT record you added for SSL activation is still present in BlueHost’s DNS. While missing this won’t cause NXDOMAIN, it’s worth confirming no accidental changes were made to your DNS zone when setting up SSL.

5. Why BlueHost’s Suggestion to Contact Google Is Unlikely Correct #

Google doesn’t manage your DNS records—BlueHost does. The SSL certificate activation only requires a temporary TXT record (which you’ve already completed), and Google has no ability to modify or remove your A records. The NXDOMAIN error is a clear sign that DNS servers aren’t finding your domain’s A record, which falls under BlueHost’s responsibility.

If after these checks your A record is correctly configured in BlueHost but global DNS still returns NXDOMAIN, push back with BlueHost support—provide the output of the dig/nslookup commands to prove the record isn’t propagating. Sometimes DNS zone files can have hidden errors (like trailing spaces or incorrect syntax) that only their support can fix.

内容的提问来源于stack exchange，提问作者Henry Li-Heng Chang