Similar case to: https://www.googlecloudcommunity.com/gc/Apigee/Apigee-X-runtime-DNS/td-p/161752
Running on Apigee X.
Have a private on prem service that I'm trying to hit from Apigee. Let's say it's https://user-api.example.com/api/v1. Proxy is configured to send a request to that URL.
Currently I have:
- Apigee X installed and working. I'm able to hit public endpoints.
- Single client VPC with single subnet (no other services in other gcp projects that I need to connect to).
- Partner inteconnect set up to connect to private on-prem network.
- DNS private forwarding zone created pointing to on prem DNS resolution server IPs. (I verified I can send a dig request from a vm in client VPC to host resolved through on prem DNS servers).
- Proxy in Apigee pointing to url that needs to be resolved through on prem DNS servers.
Ran the peering command in the above linked community post at the top of this page (omitting service so it uses the default servicenetworking.googleapis.com in the command)
gcloud services peered-dns-domains create example-com --network=my-network --dns-suffix=example.com.
Getting 503s in Apigee trying to hit the on-prem service using the url to that service that needs to be resolved by on prem DNS servers. Note, that I can send a curl request from a vm in my vpc to the on prem url and get a 400 (as expected). Wondering if there is some config that I'm missing for the request to work from Apigee given that it's working if I curl from a vm inside client VPC.
LinkedIn
Twitter
