---
title: "Cloud DNS"
description: "1 posts about Cloud DNS, summarised, each linking to the original."
---

# Cloud DNS
> 1 posts about Cloud DNS, summarised, each linking to the original.

## Articles

### [How to securely connect internal Cloud Run MCP servers to Gemini Enterprise](https://yomu.fyi/post/how-to-securely-connect-internal-cloud-run-mcp-servers-to-gemini-enter.md)
- Company: [Google](https://yomu.fyi/company/google.md)
- Author: Neeraj Agrawal
- Published: Nov 20, 2026
- Type: Tutorial

Enterprise teams using Gemini Enterprise build custom MCP servers on Cloud Run to connect AI agents to internal APIs, databases, and workflows. Three challenges arise: internal-only ingress blocks public calls, Cloud Run IAM and user OAuth 2.0 must both be verified, and Shared VPCs cannot use wildcard \*.run.app DNS zones without breaking other services. The solution uses an Egress Agent Gateway with Private Service Connect to route traffic privately into the VPC, then to Cloud Run via Private Google Access or a global PSC endpoint. FQDN-scoped Private Cloud DNS resolves only the MCP server hostname to a private VIP, avoiding DNS collisions. Gemini Enterprise sends two authorization headers: an OIDC ID token for Cloud Run IAM and the user’s OAuth 2.0 access token for application-level validation. A companion GitHub repository provides a runnable Python MCP server with OAuth 2.0 middleware and step-by-step setup scripts.
