Assigned A record for Subdomain in Cloud DNS to Compute Engine VM instance but not propagated/resolved yet

19 Views Asked by At

I've assigned an A record in Cloud DNS to one of my Compute Engine VM instances, but it's not being resolved for 12 hours.

Should I wait longer (I mean, is it OK that it's not propagated yet, after 12 hours), or did I mis-configured something in Cloud DNS panel?

Main/Parent domain (without subdomain) is assigned to another Compute Engine VM instance and it's working fine, and being resolved (tested with nslookup)

But as showing in screenshot, A record of Subdomain is not being propagated, after 12 hours.

Also, when I try to reach to subdomain in Chrome, I get an ERR_NAME_NOT_RESOLVED error. But when I try to reach VM Instance Ephemeral (Static) IP address, it works fine on 80 (HTTP).


Cloud DNS configuration


Chrome ERR_NAME_NOT_RESOLVED error


nslookup Non-existent domain result


whatsmydns.net test result

0

There are 0 best solutions below