gcloud-help/gcloud/dns/record-sets/create

NAME
    gcloud dns record-sets create - creates a record-set in a managed-zone

SYNOPSIS
    gcloud dns record-sets create DNS_NAME --type=TYPE --zone=ZONE, -z ZONE
        (--rrdatas=[RRDATA,...] | [--routing-policy-type=ROUTING_POLICY_TYPE
          (--routing-policy-data=ROUTING_POLICY_DATA
          | [--routing-policy-backup-data=ROUTING_POLICY_BACKUP_DATA
          --routing-policy-backup-data-type=ROUTING_POLICY_BACKUP_DATA_TYPE
          --routing-policy-primary-data=ROUTING_POLICY_PRIMARY_DATA
          : --backup-data-trickle-ratio=BACKUP_DATA_TRICKLE_RATIO])
          : --enable-geo-fencing --enable-health-checking])
        [--location=LOCATION] [--ttl=TTL] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    This command creates a record-set contained within the specified
    managed-zone.

EXAMPLES
    To create a record-set with dnsName foo.bar.com., record type A, rrdata
    [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone run this:

        $ gcloud dns record-sets create foo.bar.com. \
            --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone

    To create a geo routed record-set with dnsName foo.bar.com., record type A,
    routing_policy_data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6"
    and ttl 60 in my_zone.

        $ gcloud dns record-sets create foo.bar.com. \
            --routing_policy_data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\
        .6,9.8.7.6" --routing_policy_type=GEO --type=A --ttl=60 \
            --zone=my_zone --location=us-east1-a

    To create a record-set with dnsName foo.bar.com., record type A, rrdata
    [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this:

        $ gcloud dns record-sets create us-east1-a.bar.com. \
            --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \
            --location=us-east1-a

    To create a failover type health checked routed record-set with dnsName
    foo.bar.com., record type A, primary routing data "config1", backup routing
    data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6", with a trickle
    traffic ratio of 10% to the backup data, and ttl 60 in my_zone.

        $ gcloud dns record-sets create foo.bar.com. --type=A --ttl=60 \
            --zone=routing-policy-test --routing_policy_type=FAILOVER \
            --routing-policy-primary-data='config1' \
            --routing-policy-backup-data-type=GEO \
            --routing-policy-backup-data='us-centra1=1.2.3.4,2.3.4.5;us-west\
        1=3.4.5.6,9.8.7.6' --backup-data-trickle-ratio=0.1 \
            --enable-health-checking --zone=my_zone

    To create a geo fenced health checked routed record-set with dnsName
    foo.bar.com., record type A, routing-policy-data
    "us-centra1=config1,config2;us-west1=3.4.5.6,9.8.7.6", and ttl 60 in
    my_zone.

        $ gcloud dns record-sets create foo.bar.com. --type=A --ttl=60 \
            --zone=routing-policy-test --routing_policy_type=GEO \
            --routing_policy_data='us-centra1=config1,config2;us-west1=3.4.5\
        .6,9.8.7.6' --enable-health-checking --enable-geo-fencing \
            --zone=my_zone

POSITIONAL ARGUMENTS
     DNS_NAME
        DNS or domain name of the record-set.

REQUIRED FLAGS
     --type=TYPE
        DNS record type of the record-set (e.g. A, AAAA, MX etc.).

     --zone=ZONE, -z ZONE
        Name of the managed zone whose record sets you want to manage.

     Resource record sets arguments. Can specify either --rrdatas or both
     --routing-policy-data and --routing-policy-type.

     Exactly one of these must be specified:

       --rrdatas=[RRDATA,...]
          DNS data (Address/CNAME/MX info, etc.) of the record-set. This is
          RDATA; the format of this information varies depending on the type
          and class of the resource record.

       Routing policy arguments. If you specify one of --routing-policy-data or
       --routing-policy-type, you must specify both.

         --routing-policy-type=ROUTING_POLICY_TYPE
            Indicates what type of routing policy is being specified. As of
            this time, this field can take on either "WRR" for weighted round
            robin, "GEO" for geo location, or "FAILOVER" for a primary-backup
            configuration. This field cannot be modified - once a policy has a
            chosen type, the only way to change it is to delete the policy and
            add a new one with the different type. ROUTING_POLICY_TYPE must be
            one of: GEO, WRR, FAILOVER.

            This flag argument must be specified if any of the other arguments
            in this group are specified.

         --enable-geo-fencing
            Specifies whether to enable fencing for geo queries.

         --enable-health-checking
            Required if specifying forwarding rule names for rrdata.

         Routing policy data arguments. Combines routing-policy-data,
         routing-policy-primary-data, routing-policy-backup-data.

         Exactly one of these must be specified:

           --routing-policy-data=ROUTING_POLICY_DATA
              The routing policy data supports one of two formats below,
              depending on the choice of routing-policy-type.

              For --routing-policy-type = "WRR" this flag indicates the
              weighted round robin policy data. The field accepts a
              semicolon-delimited list of the format
              "${weight_percent}=${rrdata},${rrdata}". Specify weight as a
              non-negative number (0 is allowed). Ratio of traffic routed to
              the target is calculated from the ratio of individual weight over
              the total across all weights.

              For --routing-policy-type = "GEO" this flag indicates the
              geo-locations policy data. The field accepts a
              semicolon-delimited list of the format
              "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP
              address or a reference to a forwarding rule of the format
              FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full
              resource path of the forwarding rule.

           Configuration for primary backup routing policy

             --routing-policy-backup-data=ROUTING_POLICY_BACKUP_DATA
                The backup configuration for a primary backup routing policy.
                This configuration has the same format as the
                routing-policy-data argument because it is just another
                geo-locations policy.

                This flag argument must be specified if any of the other
                arguments in this group are specified.

             --routing-policy-backup-data-type=ROUTING_POLICY_BACKUP_DATA_TYPE
                For FAILOVER routing policies, the type of routing policy the
                backup data uses. Currently, this must be GEO.
                ROUTING_POLICY_BACKUP_DATA_TYPE must be (only one value is
                supported): GEO.

                This flag argument must be specified if any of the other
                arguments in this group are specified.

             --routing-policy-primary-data=ROUTING_POLICY_PRIMARY_DATA
                The primary configuration for a primary backup routing policy.
                This configuration is a list of forwarding rules of the format
                "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@scope", or the
                full resource path of the forwarding rule.

                This flag argument must be specified if any of the other
                arguments in this group are specified.

             --backup-data-trickle-ratio=BACKUP_DATA_TRICKLE_RATIO
                Specifies the percentage of traffic to send to the backup
                targets even when the primary targets are healthy.

OPTIONAL FLAGS
     --location=LOCATION
        Specifies the desired service location the request is sent to. Defaults
        to Cloud DNS global service. Use --location=global if you want to
        target the global service.

     --ttl=TTL
        TTL (time to live) for the record-set.

GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
    --help, --impersonate-service-account, --log-http, --project, --quiet,
    --trace-token, --user-output-enabled, --verbosity.

    Run $ gcloud help for details.

NOTES
    These variants are also available:

        $ gcloud alpha dns record-sets create

        $ gcloud beta dns record-sets create