Google Cloud DNS无法访问服务器求助（原使用AWS Route53）

Hey there! Since you're transitioning from AWS Route53 to Google Cloud DNS, I totally get wanting that same seamless experience. Let's break down the most common fixes for your problem—since direct IP access works, the issue is almost certainly tied to your DNS configuration.

Step 1: Verify Your DNS Record Configuration #

• Double-check that you've created A/AAAA records (for IPv4/IPv6) pointing to your server's correct public IP. It's easy to accidentally create a CNAME record with incorrect values, or mistype the IP address.
• If your server is a GCP VM, ensure its external IP is set to static—temporary ephemeral IPs change on restart, which would break DNS resolution instantly.

Step 2: Confirm Domain NS Records Point to GCP DNS Servers #

This is the most frequent pitfall when switching DNS providers:

• In your domain registrar's control panel, replace the default nameservers with the 4 NS addresses listed in your Google Cloud DNS zone details.
• To verify, run this command in your terminal:

  nslookup -type=ns yourdomain.com
  

• The output should exactly match the NS records provided by GCP. If it shows your old registrar or AWS Route53 servers, your domain isn't using GCP DNS yet.

Step 3: Check DNS Propagation Status #

DNS changes don't take effect immediately—propagation can take 15 minutes to 24 hours globally:

• Test resolution from different networks (e.g., mobile data vs. home Wi-Fi) using these commands:

  dig yourdomain.com
  nslookup yourdomain.com
  

• Use the built-in DNS Query Test tool in the GCP Console (under your DNS zone details) to confirm GCP's own servers return the correct IP.

Step 4: Validate GCP DNS Zone Settings #

• Ensure your DNS zone is set to Public (not Private) if you're hosting a public-facing service. Private zones only resolve within your GCP VPC.
• Check that the zone status is Active—if it's in a pending or error state, review your billing and permissions (though you mentioned billing is enabled, it's worth a quick check).

Step 5: Rule Out Firewall/Routing Edge Cases #

While direct IP access works, it's worth confirming:

• Your GCP VPC firewall allows inbound traffic on the ports you're using (e.g., 80 for HTTP, 443 for HTTPS) from 0.0.0.0/0 (for public access).
• There are no custom routing rules that might interfere with domain-based traffic (this is rare, but worth eliminating).

Start with verifying the NS records at your registrar—that's the number one issue when moving DNS providers. If that's set correctly, give it some time for propagation, then double-check your A/AAAA records. Let me know if any of these steps help you resolve the problem!

内容的提问来源于stack exchange，提问作者David Leonardo Andrade Bolaños