cloud not resolve CNAME in GCP Cloud DNS

Question

We have peered two VPCs. GCP & third party VPC (Aiven).

We have few services in aiven which require to talk with resources in gcp vpc such as elasticsearch, redis etc.

Let's say,

DNS-CNAME: test-elasticsearch.example.io
ES-URL: test-elasticsearch.aivencloud.com

We have a cloud DNS zone in GCP VPC. I have configured CNAME for third party service URL which can be only accessed via GCP VPC.

I'm successfully able to ping elasticsearch url from GCP VPC however, I can't ping CNAME.

FYI: the dns-zone is working good. I tested it by creating A record for the same with private ip.

In this, let me know what I can do to troubleshoot it this issue.

UPDATE: edit 1. no CNAME is working in my cloud DNS.

edit 2. resources in public subnets can resolve but not private subnet resources

kindly help

Did you put a dot at the end of the CNAME record? – Sergiusz Apr 07 '21 at 14:08 — Sergiusz, Apr 07 '21 at 14:08
yes. trailing dot is mandatory – Arvin Apr 07 '21 at 14:09 — Arvin, Apr 07 '21 at 14:09
Can you post anonymised result of ```dig -t ANY```? – Sergiusz Apr 08 '21 at 08:20 — Sergiusz, Apr 08 '21 at 08:20

score 0 · Answer 1 · answered Feb 01 '23 at 13:22

0

The problem is GCP does not resolve CNAME on private zones
I just tried to reference an AWS load balancer as a CNAME record in private zone and it just does not resolve it's ip.
GCP calls it CNAME Chasing

answered Feb 01 '23 at 13:22

123Fork

75
1
6

cloud not resolve CNAME in GCP Cloud DNS

1 Answers1