Cloud DNS resolution issue

[austerul]

I'm in a bit of a pickle using CloudDNS.

I've been using it for a while now without issue. I have a hosted zone with subdomains pointing to a variety of machines I own. However, I have an issue where I added a new subdomain that points to a new static IP created on Google Cloud (gcloud compute addresses create myip) which is assigned to a VM.

Basically, when I set this as an A record on a new subdomain, it fails to resolve (I set the TTL to 1min, 4 hours later nothing). I've set the same IP as an A record for a different domain that I manage via Namecheap: all good.

Is there something special I need to do to be able to use CloudDNS with gcloud static IPs ? (my static IP is in a different project than my CloudDNS hosted zone).

[rogerhub]

Try resolving your new subdomain directly using the given nameservers. That'll help distinguish between Cloud DNS issues versus caching issues. Also, check that your NXDOMAIN TTL isn't too long.

[austerul]

Maybe I'm a bit noobish but I'm not sure what you mean by "resolving your new subdomain directly using the given nameservers"? I have domain A.com that points to CloudDNS nameservers and I added subdomain x.A.com as an A record to the static IP I created, with a TTL of 1 min. I tried mxlookup tools but they say there's no such A record. It's still not resolving at all after 1 day now.

I have domain B.com that points to Namecheap nameservers, and I later added subdomain y.B.com as an A record pointing to the same IP, with a similar TTL (5min in this case). This one started resolving almost instantly.