Cloud DNS

  1. Internal DNS entries for instance tags

    When a tag is applied to an instance it should generate an internal dns entry.

    Example:

    tag prod-db is applied to prod-db-1 instance which has an internal ip of 10.0.0.1

    prod-db-1 would have a fqdn of: prod-db-1.c.project-1.internal and a lookup against that host from a different instance would resolve the ip to 10.0.0.1.

    I'm proposing that additional host entries be added for tags. Example:

    prod-db-tag.c.project-1.internal

    This is useful because just like tags are used for source/destination tags in the firewall they would also be useful via dns from the instances.

    Yes, it's entirely possible to write scripts that determine these…

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. SSHFP

    Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
    https://tools.ietf.org/html/rfc4255

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Rename Zone

    Just the Project GUI name, not the actual DNS name

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Issue when creating nested subdomain of verified domain through API

    Verified domain: example.com
    Subdomain: d.c.b.a.example.com

    When trying to create a nested subdomain of a verified domain, at a certain level, it errors with:
    ERROR: (gcloud.dns.managed-zones.create) HTTPError 400: Please verify ownership of the 'd.c.b.a.example.com.' domain (or a parent) at http://www.google.com/webmasters/verification/ and try again

    The weird thing is that there are no issues with creating a.example.com, b.a.example.com or c.b.a.example.com through the API (gcloud CLI or terraform).

    Also, creating the same domain via the control panel works with no issues. We are doing that currently as a workaround and importing it in the terraform state but it is cumbersome and error prone.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Cloud DNS

Categories

Feedback and Knowledge Base