Two projects run separate VPCs that are connected with VPC Network Peering. Teams want internal DNS names in each project to resolve across the peer without exposing names publicly. What should the architects implement?

DNS peering allows VPC networks connected via VPC Network Peering to resolve internal DNS names from each other's private zones. By creating DNS peering zones in both Project A and Project B, each project can reference the other's private DNS zone, enabling seamless internal name resolution without public exposure. Relying on VPC Network Peering alone is insufficient because it only provides network connectivity, not DNS resolution. Creating a Cloud DNS private managed zone in Project A and adding Project B's network would only allow Project B to resolve names in Project A, not vice-versa. A public managed zone is inappropriate for internal names and introduces unnecessary security risks.