How can we improve Compute Engine?

Permit custom DHCP options (DNS servers, domain-names)

It would be very helpful if I can specify DHCP options in my networks, minimally the DNS servers. In our use case, we have have a VPN that connects back to our internal network and large amount of infrastructure that does not have external DNS entries. (So the GCP router/DNS server can't see it).

It would be much easier if per-network we can just default these entries instead of fixing /etc/resolv.conf post-dhclient

Similarly, domain-name, search order, NTP would also be useful.

163 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Matt Lesko shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    11 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Derek Schauland commented  ·   ·  Flag as inappropriate

        This feature would be extremely helpful in the use case of extending Active Directory to GCP. Running an AD Domain entirely in GCP is possible, but extending an existing domain across a VPN to GCP where the existing Domain controllers do not have external IP addresses - nor should they.

      • Arran Peterson commented  ·   ·  Flag as inappropriate

        Running a enterprise active directory with windows domain join members servers isn’t possible. This eliminates GCP discussions with customers that are looking to move out of there existing data centres. All my customers with windows server fleets need Active Directory with integrated DNS. The option to allow the VPC to use custom name servers for internal resolution is a must. I can’t recommend GCP over Azure or AWS for windows workloads.

      • Anonymous commented  ·   ·  Flag as inappropriate

        . So Amazon give the ability to set DHCP options like nameservers to use and search suffixes. This allows us to have consistent configs among all our servers vpc/subnet.

      • Chupaka commented  ·   ·  Flag as inappropriate

        Also, DHCP Option 121 (Classless routes) so we can push custom routes to additional NICs.

      • David Miller commented  ·   ·  Flag as inappropriate

        Yes , this would be useful, as would being able to have .local data in a DNS zone of specificed domain which can be resolved to by company DNS servers

        ie we need instances and app engines in the cloud to be able to resolve domains in google cloud and in ourVPN connected subnet/sub domains.

      • David McNeely commented  ·   ·  Flag as inappropriate

        This capability would greatly simplify usage of Active Directory within GCP, since AD joined computers need to find all of the AD DNS entries which is easiest to simply run DNS on AD. But, I want to have new instances automatically point to the AD DNS, not Google DNS.
        Most of our Enterprise customers who are migrating to cloud are extending their AD into private IaaS environments and tend to run their own AD as a resource forest with it's own DNS for all VMs.

      • Maxim Doucet commented  ·   ·  Flag as inappropriate

        also note that you should add "options rotate" in /etc/resolv.conf (this will be preserved even when dhclient is used) so that the OS will try both you DNS servers *and* google DNS servers

      • Maxim Doucet commented  ·   ·  Flag as inappropriate

        You can already do this by configuring dhclient (which in turns will modify /etc/resolv.conf). The file to modify is generally "/etc/dhclient-eth0.conf" (at least on CentOS)

        It is described here: https://cloud.google.com/compute/docs/networking#internal_dns_and_resolvconf and in "man dhclient.conf"

        The idea is to use "prepend domain-search yourdomain" and "append domain-name-servers ip_of_your_dns_server" in "/etc/dhclient-eth0.conf"

      Feedback and Knowledge Base