CODEWITHSUNDEEP
google-cloud-platformgoogle-cloud-dnsgoogle-cloud-networking
Vagho
Vagho

Reputation: 117

VM instances does not use the google cloud dns forwarder to resolve

i have setup my infra on GCP and created a VPC and firewall rules to allow outgoing 53 from inside my network to the outside.

i also setup a private dns zone in google cloud and added a dns forwarder ip (e.g. 192.168.1.1) to it. i also added the network that my vm is in to the dns zone allowed list .

now when i launch my VM and try to dig to test.mydomain.com it does not work, but when i put the ip mentioned above that i used as the dns forwarder in the /etc/resolve.conf the dig works ..

what am i missing here ?

Upvotes: 1

Views: 722

Answers (1)

Adrian nieto macias
Adrian nieto macias

Reputation: 123

By default, the resolution of internal DNS names is handled by the Instance metadata server (169.254.169.254)

If you change the name server configuration for your Instance, you might not be able to use internal DNS names. Any replacement of the name server software must support the Local Subnet Routes feature of RFC 3442.

Upvotes: 0

Related Questions