Home / server / Questions / 1097452
Accepted
Vojtěch
Asked: 2022-03-31 20:52:31 +0800 CST

DNS resolving from Cloudfunctions in VPC network

  • 772

I am deploying a Cloudfunction with VPC network as follows:

gcloud beta functions deploy my-function
      --trigger-http
      --region europe-west1
      --memory 128MB
      --runtime nodejs16
      --entry-point entrypoint
      --allow-unauthenticated
      # needed to access compute instances
      # https://console.cloud.google.com/networking/connectors/list
      --vpc-connector cloud-function-connector
      # vpc connector should be used only to access private network
      --egress-settings private-ranges-only

Now, if my Cloudfunction uses IP address of compute resources, I can easily access them. However when I use their hostnames, the DNS are not resolved which ends up with:

Error: getaddrinfo ENOTFOUND my-compute-resource

What do I need to do to be able to use DNS for my compute instances?

google-cloud-platform google-compute-engine google-cloud-functions

1 Answers

  1. Best Answer

    To access a resource via a host name, you must use the Fully Qualified Domain Name (FQDN). Only using the host portion will fail.

    A Compute Engine VM has the following FQDN format:

    VM_NAME.ZONE.c.PROJECT_ID.internal

    If you only specify the VM_NAME, for which ZONE and PROJECT_ID should the request resolve to? That answer also determines which internal DNS server should be queried for the answer.

    To prevent that ambiguity, Google Cloud DNS requires FQDN.

    Internal DNS names and Shared VPC

    • 1