Apigee doesn't resolve internal DNS

[marcelocastro]

Good morning,

I configure a shared vpc for my Apigee and create a dns internal only.

When I access a compute engine in some projects that use one subnet on this shared vpc it is ok.

When I access a compute engine that my Apigee was deploy, this work fine to.

But, when I use this internal dns on proxy portal, this didn't work.

Can someone help me?

Thanks!

[dknezic]

I believe you're missing DNS peering - which forwards DNS queries for the specified namespace originating in the producer network (Apigee X VPC) to the consumer network to be resolved.

https://cloud.google.com/sdk/gcloud/reference/services/peered-dns-domains/create

One important thing to note is the trailing . in the dns suffix is important to include, otherwise you'll get an error

[marcelocastro]

I @dknezic, thanks for your reply.

I was read about this before post here, but I was make this configuration in a Shared VPC, so my service project (apigee and others) doesn't have a VPC and I can't configure DNS peering.

Interesting to tell that in a vm in apigee project I can resolve this name, but don't in portal (https://apigee.google.com/). 

Any other details to consider?

Thanks!

[bdadam]

@dknezicwhat was the resolution to this?