Score:0

GCP DNS Zone with Shared VPC - No Networks Available

bh flag

I have host project A which has a couple DNS forwarder zones configured. One of those zones is called example.com. I have a shared VPC set up between host project A and service project B. I want hosts in service project B to be able to resolve unqualified DNS lookups for the example.com zone. So it needs c.project-b.internal added to resolv.conf somehow.

To do this, I assume I need to either add a peering or forwarding zone for example.com in service project B. The problem with this however is that when doing either option, I have no networks to choose from when creating the zone so it's a useless zone. Under "Your private zone will be visible to the selected networks", the network list is always empty in the service project.

I don't want to add this entry to my /etc/resolv.conf file through host scripts or anything like that. I want this to be automatic at the project level.

Anyone have any ideas?

John Hanley avatar
cn flag
DHCP controls options such as hostname, domain, etc unless your clients are running on Windows. For Linux, you must manage your DHCP server or manually configure items such via /etc/hosts. FYI: do not cross post via multiple aliases.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.