com.amazonaws.services.route53.model.ResourceRecordSet Maven / Gradle / Ivy
Show all versions of aws-java-sdk-route53 Show documentation
/*
* Copyright 2011-2016 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
* the License. A copy of the License is located at
*
* http://aws.amazon.com/apache2.0
*
* or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
* CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
* and limitations under the License.
*/
package com.amazonaws.services.route53.model;
import java.io.Serializable;
/**
*
* Information about the resource record set to create or delete.
*
*/
public class ResourceRecordSet implements Serializable, Cloneable {
/**
*
* The name of the domain you want to perform the action on.
*
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include a
* trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you specify
* is fully qualified. This means that Amazon Route 53 treats www.example.com (without a trailing dot)
* and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and -
* (hyphen) and how to specify internationalized domain names, see DNS Domain Name Format
* in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an * character
* (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com. You
* cannot use an * for one of the middle labels, for example, marketing.*.example.com. In addition, the
* * must replace the entire label; for example, you can't specify prod*.example.com.
*
*/
private String name;
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*/
private String type;
/**
*
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates among
* multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of DNS name
* and type. Omit SetIdentifier for any other types of record sets.
*
*/
private String setIdentifier;
/**
*
* Weighted resource record sets only: Among resource record sets that have the same combination of DNS name
* and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to using the
* current resource record set. Amazon Route 53 calculates the sum of the weights for the resource record sets that
* have the same combination of DNS name and type. Amazon Route 53 then responds to queries based on the ratio of a
* resource's weight to the total. Note the following:
*
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the Name
* and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to 0 for
* a resource record set, Amazon Route 53 never responds to queries with the applicable value for that resource
* record set. However, if you set Weight to 0 for all resource record sets that have the
* same combination of DNS name and type, traffic is routed to all resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks with
* weighted resource record sets. For more information, see Options for
* Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon Route 53 Developer
* Guide.
*
*
*
*/
private Long weight;
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*/
private String region;
/**
*
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53 responds
* to DNS queries based on the geographic origin of the query. For example, if you want all queries from Africa to
* be routed to a web server with an IP address of 192.0.2.111, create a resource record set with a
* Type of A and a ContinentCode of AF.
*
*
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource record
* set for a continent and one for a country on the same continent), priority goes to the smallest geographic
* region. This allows you to route most queries for a continent to one resource and to route queries for a country
* on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that aren't
* specified in other geolocation resource record sets that have the same values for the Name and
* Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to geographic
* locations, so even if you create geolocation resource record sets that cover all seven continents, Amazon Route
* 53 will receive some DNS queries from locations that it can't identify. We recommend that you create a resource
* record set for which the value of CountryCode is *, which handles both queries that
* come from locations for which you haven't created geolocation resource record sets and queries from IP addresses
* that aren't mapped to a location. If you don't create a * resource record set, Amazon Route 53
* returns a "no answer" response for queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name and
* Type elements as geolocation resource record sets.
*
*/
private GeoLocation geoLocation;
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*/
private String failover;
/**
*
* The resource record cache time to live (TTL), in seconds. Note the following:
*
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a HealthCheckId
* element), we recommend that you specify a TTL of 60 seconds or less so clients respond quickly to
* changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record sets
* must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for which
* the alias target is an ELB load balancer, we recommend that you specify a TTL of 60 seconds for all
* of the non-alias weighted resource record sets that have the same name and type. Values other than 60 seconds
* (the TTL for load balancers) will change the effect of the values that you specify for Weight.
*
*
*
*/
private Long tTL;
/**
*
* Information about the resource records to act upon.
*
*
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*
*/
private com.amazonaws.internal.SdkInternalList resourceRecords;
/**
*
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted zone is
* unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*
*/
private AliasTarget aliasTarget;
/**
*
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a health
* check is passing, include the HealthCheckId element and specify the ID of the applicable health
* check.
*
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on the
* status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover resource
* record set, and you specify health check IDs for all of the resource record sets. If the health check for one
* resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops responding to queries using
* the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted alias,
* latency alias, geolocation alias, or failover alias resource record set, and you specify health check IDs for all
* of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for example, the
* endpoint specified by the IP address in the Value element. When you add a HealthCheckId
* element to a resource record set, Amazon Route 53 checks the health of the endpoint that you specified in the
* health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource record
* set for the larger, associated geographic region. For example, suppose you have resource record sets for a state
* in the United States, for the United States, for North America, and for all locations. If the endpoint for the
* state resource record set is unhealthy, Amazon Route 53 checks the resource record sets for the United States,
* for North America, and for all locations (a resource record set for which the value of CountryCode
* is *), in that order, until it finds a resource record set for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate health
* check for each endpoint. For example, create a health check for each HTTP server that is serving
* content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-1-www.example.com), not the name of the resource record
* sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and then associate the health check with those resource record sets,
* health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*/
private String healthCheckId;
/**
*
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created this
* resource record set for.
*
*
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set automatically. If
* you delete the resource record set by using ChangeResourceRecordSets, Amazon Route 53 doesn't
* automatically delete the traffic policy instance, and you'll continue to be charged for it even though it's no
* longer in use.
*
*
*/
private String trafficPolicyInstanceId;
/**
* Default constructor for ResourceRecordSet object. Callers should use the setter or fluent setter (with...)
* methods to initialize the object after creating it.
*/
public ResourceRecordSet() {
}
/**
* Constructs a new ResourceRecordSet object. Callers should use the setter or fluent setter (with...) methods to
* initialize any additional object members.
*
* @param name
* The name of the domain you want to perform the action on.
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include
* a trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you
* specify is fully qualified. This means that Amazon Route 53 treats www.example.com (without a
* trailing dot) and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and
* - (hyphen) and how to specify internationalized domain names, see DNS Domain Name
* Format in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an *
* character (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com
* . You cannot use an * for one of the middle labels, for example, marketing.*.example.com. In
* addition, the * must replace the entire label; for example, you can't specify
* prod*.example.com.
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
*/
public ResourceRecordSet(String name, String type) {
setName(name);
setType(type);
}
/**
* Constructs a new ResourceRecordSet object. Callers should use the setter or fluent setter (with...) methods to
* initialize any additional object members.
*
* @param name
* The name of the domain you want to perform the action on.
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include
* a trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you
* specify is fully qualified. This means that Amazon Route 53 treats www.example.com (without a
* trailing dot) and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and
* - (hyphen) and how to specify internationalized domain names, see DNS Domain Name
* Format in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an *
* character (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com
* . You cannot use an * for one of the middle labels, for example, marketing.*.example.com. In
* addition, the * must replace the entire label; for example, you can't specify
* prod*.example.com.
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
*/
public ResourceRecordSet(String name, RRType type) {
setName(name);
setType(type.toString());
}
/**
*
* The name of the domain you want to perform the action on.
*
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include a
* trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you specify
* is fully qualified. This means that Amazon Route 53 treats www.example.com (without a trailing dot)
* and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and -
* (hyphen) and how to specify internationalized domain names, see DNS Domain Name Format
* in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an * character
* (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com. You
* cannot use an * for one of the middle labels, for example, marketing.*.example.com. In addition, the
* * must replace the entire label; for example, you can't specify prod*.example.com.
*
*
* @param name
* The name of the domain you want to perform the action on.
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include
* a trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you
* specify is fully qualified. This means that Amazon Route 53 treats www.example.com (without a
* trailing dot) and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and
* - (hyphen) and how to specify internationalized domain names, see DNS Domain Name
* Format in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an *
* character (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com
* . You cannot use an * for one of the middle labels, for example, marketing.*.example.com. In
* addition, the * must replace the entire label; for example, you can't specify
* prod*.example.com.
*/
public void setName(String name) {
this.name = name;
}
/**
*
* The name of the domain you want to perform the action on.
*
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include a
* trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you specify
* is fully qualified. This means that Amazon Route 53 treats www.example.com (without a trailing dot)
* and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and -
* (hyphen) and how to specify internationalized domain names, see DNS Domain Name Format
* in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an * character
* (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com. You
* cannot use an * for one of the middle labels, for example, marketing.*.example.com. In addition, the
* * must replace the entire label; for example, you can't specify prod*.example.com.
*
*
* @return The name of the domain you want to perform the action on.
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally
* include a trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name
* that you specify is fully qualified. This means that Amazon Route 53 treats www.example.com
* (without a trailing dot) and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and
* - (hyphen) and how to specify internationalized domain names, see DNS Domain Name
* Format in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an *
* character (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example,
* *.example.com. You cannot use an * for one of the middle labels, for example,
* marketing.*.example.com. In addition, the * must replace the entire label; for example, you
* can't specify prod*.example.com.
*/
public String getName() {
return this.name;
}
/**
*
* The name of the domain you want to perform the action on.
*
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include a
* trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you specify
* is fully qualified. This means that Amazon Route 53 treats www.example.com (without a trailing dot)
* and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and -
* (hyphen) and how to specify internationalized domain names, see DNS Domain Name Format
* in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an * character
* (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com. You
* cannot use an * for one of the middle labels, for example, marketing.*.example.com. In addition, the
* * must replace the entire label; for example, you can't specify prod*.example.com.
*
*
* @param name
* The name of the domain you want to perform the action on.
*
* Enter a fully qualified domain name, for example, www.example.com. You can optionally include
* a trailing dot. If you omit the trailing dot, Amazon Route 53 still assumes that the domain name that you
* specify is fully qualified. This means that Amazon Route 53 treats www.example.com (without a
* trailing dot) and www.example.com. (with a trailing dot) as identical.
*
*
* For information about how to specify characters other than a-z, 0-9, and
* - (hyphen) and how to specify internationalized domain names, see DNS Domain Name
* Format in the Amazon Route 53 Developer Guide.
*
*
* You can use the asterisk (*) wildcard to replace the leftmost label in a domain name. For example,
* *.example.com. Note the following:
*
*
* -
*
* The * must replace the entire label. For example, you can't specify *prod.example.com or
* prod*.example.com.
*
*
* -
*
* The * can't replace any of the middle labels, for example, marketing.*.example.com.
*
*
* -
*
* If you include * in any position other than the leftmost label in a domain name, DNS treats it as an *
* character (ASCII 42), not as a wildcard.
*
*
*
* You can't use the * wildcard for resource records sets that have a type of NS.
*
*
*
*
* You can use the * wildcard as the leftmost label in a domain name, for example, *.example.com
* . You cannot use an * for one of the middle labels, for example, marketing.*.example.com. In
* addition, the * must replace the entire label; for example, you can't specify
* prod*.example.com.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withName(String name) {
setName(name);
return this;
}
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
* @see RRType
*/
public void setType(String type) {
this.type = type;
}
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*
* @return The DNS record type. For information about different record types and how data is encoded for them, see
* Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
* @see RRType
*/
public String getType() {
return this.type;
}
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see RRType
*/
public ResourceRecordSet withType(String type) {
setType(type);
return this;
}
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
* @see RRType
*/
public void setType(RRType type) {
this.type = type.toString();
}
/**
*
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS Resource
* Record Types in the Amazon Route 53 Developer Guide.
*
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA | SPF |
* SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A | AAAA
* | CNAME | MX | NAPTR | PTR | SPF |
* SRV | TXT. When creating a group of weighted, latency, geolocation, or failover
* resource record sets, specify the same value for all of the resource record sets in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no longer
* recommend that you create resource record sets for which the value of Type is SPF. RFC
* 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
* to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS Record
* Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for which
* you're creating the alias. Specify any value except NS or SOA.
*
*
*
*
* @param type
* The DNS record type. For information about different record types and how data is encoded for them, see Supported DNS
* Resource Record Types in the Amazon Route 53 Developer Guide.
*
* Valid values for basic resource record sets: A | AAAA | CNAME |
* MX | NAPTR | NS | PTR | SOA |
* SPF | SRV | TXT
*
*
* Values for weighted, latency, geolocation, and failover resource record sets: A |
* AAAA | CNAME | MX | NAPTR | PTR |
* SPF | SRV | TXT. When creating a group of weighted, latency,
* geolocation, or failover resource record sets, specify the same value for all of the resource record sets
* in the group.
*
*
*
* SPF records were formerly used to verify the identity of the sender of email messages. However, we no
* longer recommend that you create resource record sets for which the value of Type is
* SPF. RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
* Version 1, has been updated to say,
* "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues. Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it."
* In RFC 7208, see section 14.1, The SPF DNS
* Record Type.
*
*
*
* Values for alias resource record sets:
*
*
* -
*
* CloudFront distributions: A
*
*
* -
*
* Elastic Beanstalk environment that has a regionalized subdomain: A
*
*
* -
*
* ELB load balancers: A | AAAA
*
*
* -
*
* Amazon S3 buckets: A
*
*
* -
*
* Another resource record set in this hosted zone: Specify the type of the resource record set for
* which you're creating the alias. Specify any value except NS or SOA.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see RRType
*/
public ResourceRecordSet withType(RRType type) {
setType(type);
return this;
}
/**
*
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates among
* multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of DNS name
* and type. Omit SetIdentifier for any other types of record sets.
*
*
* @param setIdentifier
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates
* among multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of
* DNS name and type. Omit SetIdentifier for any other types of record sets.
*/
public void setSetIdentifier(String setIdentifier) {
this.setIdentifier = setIdentifier;
}
/**
*
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates among
* multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of DNS name
* and type. Omit SetIdentifier for any other types of record sets.
*
*
* @return Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates
* among multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of
* DNS name and type. Omit SetIdentifier for any other types of record sets.
*/
public String getSetIdentifier() {
return this.setIdentifier;
}
/**
*
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates among
* multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of DNS name
* and type. Omit SetIdentifier for any other types of record sets.
*
*
* @param setIdentifier
* Weighted, Latency, Geo, and Failover resource record sets only: An identifier that differentiates
* among multiple resource record sets that have the same combination of DNS name and type. The value of
* SetIdentifier must be unique for each resource record set that has the same combination of
* DNS name and type. Omit SetIdentifier for any other types of record sets.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withSetIdentifier(String setIdentifier) {
setSetIdentifier(setIdentifier);
return this;
}
/**
*
* Weighted resource record sets only: Among resource record sets that have the same combination of DNS name
* and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to using the
* current resource record set. Amazon Route 53 calculates the sum of the weights for the resource record sets that
* have the same combination of DNS name and type. Amazon Route 53 then responds to queries based on the ratio of a
* resource's weight to the total. Note the following:
*
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the Name
* and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to 0 for
* a resource record set, Amazon Route 53 never responds to queries with the applicable value for that resource
* record set. However, if you set Weight to 0 for all resource record sets that have the
* same combination of DNS name and type, traffic is routed to all resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks with
* weighted resource record sets. For more information, see Options for
* Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon Route 53 Developer
* Guide.
*
*
*
*
* @param weight
* Weighted resource record sets only: Among resource record sets that have the same combination of
* DNS name and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to
* using the current resource record set. Amazon Route 53 calculates the sum of the weights for the resource
* record sets that have the same combination of DNS name and type. Amazon Route 53 then responds to queries
* based on the ratio of a resource's weight to the total. Note the following:
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the
* Name and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to
* 0 for a resource record set, Amazon Route 53 never responds to queries with the applicable
* value for that resource record set. However, if you set Weight to 0 for all
* resource record sets that have the same combination of DNS name and type, traffic is routed to all
* resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks
* with weighted resource record sets. For more information, see Options for Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon
* Route 53 Developer Guide.
*
*
*/
public void setWeight(Long weight) {
this.weight = weight;
}
/**
*
* Weighted resource record sets only: Among resource record sets that have the same combination of DNS name
* and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to using the
* current resource record set. Amazon Route 53 calculates the sum of the weights for the resource record sets that
* have the same combination of DNS name and type. Amazon Route 53 then responds to queries based on the ratio of a
* resource's weight to the total. Note the following:
*
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the Name
* and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to 0 for
* a resource record set, Amazon Route 53 never responds to queries with the applicable value for that resource
* record set. However, if you set Weight to 0 for all resource record sets that have the
* same combination of DNS name and type, traffic is routed to all resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks with
* weighted resource record sets. For more information, see Options for
* Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon Route 53 Developer
* Guide.
*
*
*
*
* @return Weighted resource record sets only: Among resource record sets that have the same combination of
* DNS name and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to
* using the current resource record set. Amazon Route 53 calculates the sum of the weights for the resource
* record sets that have the same combination of DNS name and type. Amazon Route 53 then responds to queries
* based on the ratio of a resource's weight to the total. Note the following:
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for
* the Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the
* Name and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to
* 0 for a resource record set, Amazon Route 53 never responds to queries with the applicable
* value for that resource record set. However, if you set Weight to 0 for all
* resource record sets that have the same combination of DNS name and type, traffic is routed to all
* resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks
* with weighted resource record sets. For more information, see Options for Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon
* Route 53 Developer Guide.
*
*
*/
public Long getWeight() {
return this.weight;
}
/**
*
* Weighted resource record sets only: Among resource record sets that have the same combination of DNS name
* and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to using the
* current resource record set. Amazon Route 53 calculates the sum of the weights for the resource record sets that
* have the same combination of DNS name and type. Amazon Route 53 then responds to queries based on the ratio of a
* resource's weight to the total. Note the following:
*
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the Name
* and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to 0 for
* a resource record set, Amazon Route 53 never responds to queries with the applicable value for that resource
* record set. However, if you set Weight to 0 for all resource record sets that have the
* same combination of DNS name and type, traffic is routed to all resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks with
* weighted resource record sets. For more information, see Options for
* Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon Route 53 Developer
* Guide.
*
*
*
*
* @param weight
* Weighted resource record sets only: Among resource record sets that have the same combination of
* DNS name and type, a value that determines the proportion of DNS queries that Amazon Route 53 responds to
* using the current resource record set. Amazon Route 53 calculates the sum of the weights for the resource
* record sets that have the same combination of DNS name and type. Amazon Route 53 then responds to queries
* based on the ratio of a resource's weight to the total. Note the following:
*
* -
*
* You must specify a value for the Weight element for every weighted resource record set.
*
*
* -
*
* You can only specify one ResourceRecord per weighted resource record set.
*
*
* -
*
* You cannot create latency, failover, or geolocation resource record sets that have the same values for the
* Name and Type elements as weighted resource record sets.
*
*
* -
*
* You can create a maximum of 100 weighted resource record sets that have the same values for the
* Name and Type elements.
*
*
* -
*
* For weighted (but not weighted alias) resource record sets, if you set Weight to
* 0 for a resource record set, Amazon Route 53 never responds to queries with the applicable
* value for that resource record set. However, if you set Weight to 0 for all
* resource record sets that have the same combination of DNS name and type, traffic is routed to all
* resources with equal probability.
*
*
* The effect of setting Weight to 0 is different when you associate health checks
* with weighted resource record sets. For more information, see Options for Configuring Amazon Route 53 Active-Active and Active-Passive Failover in the Amazon
* Route 53 Developer Guide.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withWeight(Long weight) {
setWeight(weight);
return this;
}
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*
* @param region
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified
* in this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2
* instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on
* the record type.
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency
* resource record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency
* between the end user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is
* associated with the selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53
* will choose the region with the best latency from among the regions for which you create latency resource
* record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
* @see ResourceRecordSetRegion
*/
public void setRegion(String region) {
this.region = region;
}
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*
* @return Latency-based resource record sets only: The Amazon EC2 region where the resource that is
* specified in this resource record set resides. The resource typically is an AWS resource, such as an
* Amazon EC2 instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name,
* depending on the record type.
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency
* resource record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency
* between the end user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is
* associated with the selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53
* will choose the region with the best latency from among the regions for which you create latency resource
* record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name
* and Type elements as latency resource record sets.
*
*
* @see ResourceRecordSetRegion
*/
public String getRegion() {
return this.region;
}
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*
* @param region
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified
* in this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2
* instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on
* the record type.
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency
* resource record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency
* between the end user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is
* associated with the selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53
* will choose the region with the best latency from among the regions for which you create latency resource
* record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see ResourceRecordSetRegion
*/
public ResourceRecordSet withRegion(String region) {
setRegion(region);
return this;
}
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*
* @param region
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified
* in this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2
* instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on
* the record type.
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency
* resource record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency
* between the end user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is
* associated with the selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53
* will choose the region with the best latency from among the regions for which you create latency resource
* record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
* @see ResourceRecordSetRegion
*/
public void setRegion(ResourceRecordSetRegion region) {
this.region = region.toString();
}
/**
*
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified in
* this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2 instance or an
* ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on the record type.
*
*
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency resource
* record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency between the end
* user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is associated with the
* selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53 will
* choose the region with the best latency from among the regions for which you create latency resource record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
*
*
* @param region
* Latency-based resource record sets only: The Amazon EC2 region where the resource that is specified
* in this resource record set resides. The resource typically is an AWS resource, such as an Amazon EC2
* instance or an ELB load balancer, and is referred to by an IP address or a DNS domain name, depending on
* the record type.
*
* Creating latency and latency alias resource record sets in private hosted zones is not supported.
*
*
*
* When Amazon Route 53 receives a DNS query for a domain name and type for which you have created latency
* resource record sets, Amazon Route 53 selects the latency resource record set that has the lowest latency
* between the end user and the associated Amazon EC2 region. Amazon Route 53 then returns the value that is
* associated with the selected resource record set.
*
*
* Note the following:
*
*
* -
*
* You can only specify one ResourceRecord per latency resource record set.
*
*
* -
*
* You can only create one latency resource record set for each Amazon EC2 region.
*
*
* -
*
* You are not required to create latency resource record sets for all Amazon EC2 regions. Amazon Route 53
* will choose the region with the best latency from among the regions for which you create latency resource
* record sets.
*
*
* -
*
* You cannot create non-latency resource record sets that have the same values for the Name and
* Type elements as latency resource record sets.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see ResourceRecordSetRegion
*/
public ResourceRecordSet withRegion(ResourceRecordSetRegion region) {
setRegion(region);
return this;
}
/**
*
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53 responds
* to DNS queries based on the geographic origin of the query. For example, if you want all queries from Africa to
* be routed to a web server with an IP address of 192.0.2.111, create a resource record set with a
* Type of A and a ContinentCode of AF.
*
*
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource record
* set for a continent and one for a country on the same continent), priority goes to the smallest geographic
* region. This allows you to route most queries for a continent to one resource and to route queries for a country
* on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that aren't
* specified in other geolocation resource record sets that have the same values for the Name and
* Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to geographic
* locations, so even if you create geolocation resource record sets that cover all seven continents, Amazon Route
* 53 will receive some DNS queries from locations that it can't identify. We recommend that you create a resource
* record set for which the value of CountryCode is *, which handles both queries that
* come from locations for which you haven't created geolocation resource record sets and queries from IP addresses
* that aren't mapped to a location. If you don't create a * resource record set, Amazon Route 53
* returns a "no answer" response for queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name and
* Type elements as geolocation resource record sets.
*
*
* @param geoLocation
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53
* responds to DNS queries based on the geographic origin of the query. For example, if you want all queries
* from Africa to be routed to a web server with an IP address of 192.0.2.111, create a resource
* record set with a Type of A and a ContinentCode of AF
* .
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource
* record set for a continent and one for a country on the same continent), priority goes to the smallest
* geographic region. This allows you to route most queries for a continent to one resource and to route
* queries for a country on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that
* aren't specified in other geolocation resource record sets that have the same values for the
* Name and Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to
* geographic locations, so even if you create geolocation resource record sets that cover all seven
* continents, Amazon Route 53 will receive some DNS queries from locations that it can't identify. We
* recommend that you create a resource record set for which the value of CountryCode is
* *, which handles both queries that come from locations for which you haven't created
* geolocation resource record sets and queries from IP addresses that aren't mapped to a location. If you
* don't create a * resource record set, Amazon Route 53 returns a "no answer" response for
* queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name
* and Type elements as geolocation resource record sets.
*/
public void setGeoLocation(GeoLocation geoLocation) {
this.geoLocation = geoLocation;
}
/**
*
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53 responds
* to DNS queries based on the geographic origin of the query. For example, if you want all queries from Africa to
* be routed to a web server with an IP address of 192.0.2.111, create a resource record set with a
* Type of A and a ContinentCode of AF.
*
*
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource record
* set for a continent and one for a country on the same continent), priority goes to the smallest geographic
* region. This allows you to route most queries for a continent to one resource and to route queries for a country
* on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that aren't
* specified in other geolocation resource record sets that have the same values for the Name and
* Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to geographic
* locations, so even if you create geolocation resource record sets that cover all seven continents, Amazon Route
* 53 will receive some DNS queries from locations that it can't identify. We recommend that you create a resource
* record set for which the value of CountryCode is *, which handles both queries that
* come from locations for which you haven't created geolocation resource record sets and queries from IP addresses
* that aren't mapped to a location. If you don't create a * resource record set, Amazon Route 53
* returns a "no answer" response for queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name and
* Type elements as geolocation resource record sets.
*
*
* @return Geo location resource record sets only: A complex type that lets you control how Amazon Route 53
* responds to DNS queries based on the geographic origin of the query. For example, if you want all queries
* from Africa to be routed to a web server with an IP address of 192.0.2.111, create a
* resource record set with a Type of A and a ContinentCode of
* AF.
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource
* record set for a continent and one for a country on the same continent), priority goes to the smallest
* geographic region. This allows you to route most queries for a continent to one resource and to route
* queries for a country on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that
* aren't specified in other geolocation resource record sets that have the same values for the
* Name and Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to
* geographic locations, so even if you create geolocation resource record sets that cover all seven
* continents, Amazon Route 53 will receive some DNS queries from locations that it can't identify. We
* recommend that you create a resource record set for which the value of CountryCode is
* *, which handles both queries that come from locations for which you haven't created
* geolocation resource record sets and queries from IP addresses that aren't mapped to a location. If you
* don't create a * resource record set, Amazon Route 53 returns a "no answer" response for
* queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the
* Name and Type elements as geolocation resource record sets.
*/
public GeoLocation getGeoLocation() {
return this.geoLocation;
}
/**
*
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53 responds
* to DNS queries based on the geographic origin of the query. For example, if you want all queries from Africa to
* be routed to a web server with an IP address of 192.0.2.111, create a resource record set with a
* Type of A and a ContinentCode of AF.
*
*
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource record
* set for a continent and one for a country on the same continent), priority goes to the smallest geographic
* region. This allows you to route most queries for a continent to one resource and to route queries for a country
* on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that aren't
* specified in other geolocation resource record sets that have the same values for the Name and
* Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to geographic
* locations, so even if you create geolocation resource record sets that cover all seven continents, Amazon Route
* 53 will receive some DNS queries from locations that it can't identify. We recommend that you create a resource
* record set for which the value of CountryCode is *, which handles both queries that
* come from locations for which you haven't created geolocation resource record sets and queries from IP addresses
* that aren't mapped to a location. If you don't create a * resource record set, Amazon Route 53
* returns a "no answer" response for queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name and
* Type elements as geolocation resource record sets.
*
*
* @param geoLocation
* Geo location resource record sets only: A complex type that lets you control how Amazon Route 53
* responds to DNS queries based on the geographic origin of the query. For example, if you want all queries
* from Africa to be routed to a web server with an IP address of 192.0.2.111, create a resource
* record set with a Type of A and a ContinentCode of AF
* .
*
* Creating geolocation and geolocation alias resource record sets in private hosted zones is not supported.
*
*
*
* If you create separate resource record sets for overlapping geographic regions (for example, one resource
* record set for a continent and one for a country on the same continent), priority goes to the smallest
* geographic region. This allows you to route most queries for a continent to one resource and to route
* queries for a country on that continent to a different resource.
*
*
* You cannot create two geolocation resource record sets that specify the same geographic location.
*
*
* The value * in the CountryCode element matches all geographic locations that
* aren't specified in other geolocation resource record sets that have the same values for the
* Name and Type elements.
*
*
*
* Geolocation works by mapping IP addresses to locations. However, some IP addresses aren't mapped to
* geographic locations, so even if you create geolocation resource record sets that cover all seven
* continents, Amazon Route 53 will receive some DNS queries from locations that it can't identify. We
* recommend that you create a resource record set for which the value of CountryCode is
* *, which handles both queries that come from locations for which you haven't created
* geolocation resource record sets and queries from IP addresses that aren't mapped to a location. If you
* don't create a * resource record set, Amazon Route 53 returns a "no answer" response for
* queries from those locations.
*
*
*
* You cannot create non-geolocation resource record sets that have the same values for the Name
* and Type elements as geolocation resource record sets.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withGeoLocation(GeoLocation geoLocation) {
setGeoLocation(geoLocation);
return this;
}
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*
* @param failover
* Failover resource record sets only: To configure failover, you add the Failover
* element to two resource record sets. For one resource record set, you specify PRIMARY as the
* value for Failover; for the other resource record set, you specify SECONDARY. In
* addition, you include the HealthCheckId element and specify the health check that you want
* Amazon Route 53 to perform for each resource record set.
*
* Except where noted, the following failover behaviors assume that you have included the
* HealthCheckId element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the secondary resource
* record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon
* Route 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the primary resource
* record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the
* primary resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the
* applicable value from the secondary resource record set. This is true regardless of the health of the
* associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name
* and Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth
* element and set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the
* Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
* @see ResourceRecordSetFailover
*/
public void setFailover(String failover) {
this.failover = failover;
}
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*
* @return Failover resource record sets only: To configure failover, you add the Failover
* element to two resource record sets. For one resource record set, you specify PRIMARY as the
* value for Failover; for the other resource record set, you specify SECONDARY.
* In addition, you include the HealthCheckId element and specify the health check that you
* want Amazon Route 53 to perform for each resource record set.
*
* Except where noted, the following failover behaviors assume that you have included the
* HealthCheckId element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the secondary resource
* record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy,
* Amazon Route 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the primary resource
* record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the
* primary resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the
* applicable value from the secondary resource record set. This is true regardless of the health of the
* associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name
* and Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth
* element and set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the
* Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
* @see ResourceRecordSetFailover
*/
public String getFailover() {
return this.failover;
}
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*
* @param failover
* Failover resource record sets only: To configure failover, you add the Failover
* element to two resource record sets. For one resource record set, you specify PRIMARY as the
* value for Failover; for the other resource record set, you specify SECONDARY. In
* addition, you include the HealthCheckId element and specify the health check that you want
* Amazon Route 53 to perform for each resource record set.
*
* Except where noted, the following failover behaviors assume that you have included the
* HealthCheckId element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the secondary resource
* record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon
* Route 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the primary resource
* record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the
* primary resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the
* applicable value from the secondary resource record set. This is true regardless of the health of the
* associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name
* and Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth
* element and set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the
* Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
* @return Returns a reference to this object so that method calls can be chained together.
* @see ResourceRecordSetFailover
*/
public ResourceRecordSet withFailover(String failover) {
setFailover(failover);
return this;
}
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*
* @param failover
* Failover resource record sets only: To configure failover, you add the Failover
* element to two resource record sets. For one resource record set, you specify PRIMARY as the
* value for Failover; for the other resource record set, you specify SECONDARY. In
* addition, you include the HealthCheckId element and specify the health check that you want
* Amazon Route 53 to perform for each resource record set.
*
* Except where noted, the following failover behaviors assume that you have included the
* HealthCheckId element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the secondary resource
* record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon
* Route 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the primary resource
* record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the
* primary resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the
* applicable value from the secondary resource record set. This is true regardless of the health of the
* associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name
* and Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth
* element and set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the
* Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
* @see ResourceRecordSetFailover
*/
public void setFailover(ResourceRecordSetFailover failover) {
this.failover = failover.toString();
}
/**
*
* Failover resource record sets only: To configure failover, you add the Failover element to
* two resource record sets. For one resource record set, you specify PRIMARY as the value for
* Failover; for the other resource record set, you specify SECONDARY. In addition, you
* include the HealthCheckId element and specify the health check that you want Amazon Route 53 to
* perform for each resource record set.
*
*
* Except where noted, the following failover behaviors assume that you have included the HealthCheckId
* element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the secondary resource record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon Route
* 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the applicable
* value from the primary resource record set regardless of the health of the primary resource record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the primary
* resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the applicable value from
* the secondary resource record set. This is true regardless of the health of the associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name and
* Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth element and
* set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the Amazon
* Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
*
*
* @param failover
* Failover resource record sets only: To configure failover, you add the Failover
* element to two resource record sets. For one resource record set, you specify PRIMARY as the
* value for Failover; for the other resource record set, you specify SECONDARY. In
* addition, you include the HealthCheckId element and specify the health check that you want
* Amazon Route 53 to perform for each resource record set.
*
* Except where noted, the following failover behaviors assume that you have included the
* HealthCheckId element in both resource record sets:
*
*
* -
*
* When the primary resource record set is healthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the secondary resource
* record set.
*
*
* -
*
* When the primary resource record set is unhealthy and the secondary resource record set is healthy, Amazon
* Route 53 responds to DNS queries with the applicable value from the secondary resource record set.
*
*
* -
*
* When the secondary resource record set is unhealthy, Amazon Route 53 responds to DNS queries with the
* applicable value from the primary resource record set regardless of the health of the primary resource
* record set.
*
*
* -
*
* If you omit the HealthCheckId element for the secondary resource record set, and if the
* primary resource record set is unhealthy, Amazon Route 53 always responds to DNS queries with the
* applicable value from the secondary resource record set. This is true regardless of the health of the
* associated endpoint.
*
*
*
*
* You cannot create non-failover resource record sets that have the same values for the Name
* and Type elements as failover resource record sets.
*
*
* For failover alias resource record sets, you must also include the EvaluateTargetHealth
* element and set the value to true.
*
*
* For more information about configuring failover for Amazon Route 53, see the following topics in the
* Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* Valid values: PRIMARY | SECONDARY
* @return Returns a reference to this object so that method calls can be chained together.
* @see ResourceRecordSetFailover
*/
public ResourceRecordSet withFailover(ResourceRecordSetFailover failover) {
setFailover(failover);
return this;
}
/**
*
* The resource record cache time to live (TTL), in seconds. Note the following:
*
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a HealthCheckId
* element), we recommend that you specify a TTL of 60 seconds or less so clients respond quickly to
* changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record sets
* must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for which
* the alias target is an ELB load balancer, we recommend that you specify a TTL of 60 seconds for all
* of the non-alias weighted resource record sets that have the same name and type. Values other than 60 seconds
* (the TTL for load balancers) will change the effect of the values that you specify for Weight.
*
*
*
*
* @param tTL
* The resource record cache time to live (TTL), in seconds. Note the following:
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a
* HealthCheckId element), we recommend that you specify a TTL of 60 seconds or
* less so clients respond quickly to changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record
* sets must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for
* which the alias target is an ELB load balancer, we recommend that you specify a TTL of 60
* seconds for all of the non-alias weighted resource record sets that have the same name and type. Values
* other than 60 seconds (the TTL for load balancers) will change the effect of the values that you specify
* for Weight.
*
*
*/
public void setTTL(Long tTL) {
this.tTL = tTL;
}
/**
*
* The resource record cache time to live (TTL), in seconds. Note the following:
*
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a HealthCheckId
* element), we recommend that you specify a TTL of 60 seconds or less so clients respond quickly to
* changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record sets
* must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for which
* the alias target is an ELB load balancer, we recommend that you specify a TTL of 60 seconds for all
* of the non-alias weighted resource record sets that have the same name and type. Values other than 60 seconds
* (the TTL for load balancers) will change the effect of the values that you specify for Weight.
*
*
*
*
* @return The resource record cache time to live (TTL), in seconds. Note the following:
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a
* HealthCheckId element), we recommend that you specify a TTL of 60 seconds or
* less so clients respond quickly to changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record
* sets must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for
* which the alias target is an ELB load balancer, we recommend that you specify a TTL of 60
* seconds for all of the non-alias weighted resource record sets that have the same name and type. Values
* other than 60 seconds (the TTL for load balancers) will change the effect of the values that you specify
* for Weight.
*
*
*/
public Long getTTL() {
return this.tTL;
}
/**
*
* The resource record cache time to live (TTL), in seconds. Note the following:
*
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a HealthCheckId
* element), we recommend that you specify a TTL of 60 seconds or less so clients respond quickly to
* changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record sets
* must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for which
* the alias target is an ELB load balancer, we recommend that you specify a TTL of 60 seconds for all
* of the non-alias weighted resource record sets that have the same name and type. Values other than 60 seconds
* (the TTL for load balancers) will change the effect of the values that you specify for Weight.
*
*
*
*
* @param tTL
* The resource record cache time to live (TTL), in seconds. Note the following:
*
* -
*
* If you're creating an alias resource record set, omit TTL. Amazon Route 53 uses the value of
* TTL for the alias target.
*
*
* -
*
* If you're associating this resource record set with a health check (if you're adding a
* HealthCheckId element), we recommend that you specify a TTL of 60 seconds or
* less so clients respond quickly to changes in health status.
*
*
* -
*
* All of the resource record sets in a group of weighted, latency, geolocation, or failover resource record
* sets must have the same value for TTL.
*
*
* -
*
* If a group of weighted resource record sets includes one or more weighted alias resource record sets for
* which the alias target is an ELB load balancer, we recommend that you specify a TTL of 60
* seconds for all of the non-alias weighted resource record sets that have the same name and type. Values
* other than 60 seconds (the TTL for load balancers) will change the effect of the values that you specify
* for Weight.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withTTL(Long tTL) {
setTTL(tTL);
return this;
}
/**
*
* Information about the resource records to act upon.
*
*
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*
*
* @return Information about the resource records to act upon.
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*/
public java.util.List getResourceRecords() {
if (resourceRecords == null) {
resourceRecords = new com.amazonaws.internal.SdkInternalList();
}
return resourceRecords;
}
/**
*
* Information about the resource records to act upon.
*
*
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*
*
* @param resourceRecords
* Information about the resource records to act upon.
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*/
public void setResourceRecords(java.util.Collection resourceRecords) {
if (resourceRecords == null) {
this.resourceRecords = null;
return;
}
this.resourceRecords = new com.amazonaws.internal.SdkInternalList(resourceRecords);
}
/**
*
* Information about the resource records to act upon.
*
*
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setResourceRecords(java.util.Collection)} or {@link #withResourceRecords(java.util.Collection)} if you
* want to override the existing values.
*
*
* @param resourceRecords
* Information about the resource records to act upon.
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withResourceRecords(ResourceRecord... resourceRecords) {
if (this.resourceRecords == null) {
setResourceRecords(new com.amazonaws.internal.SdkInternalList(resourceRecords.length));
}
for (ResourceRecord ele : resourceRecords) {
this.resourceRecords.add(ele);
}
return this;
}
/**
*
* Information about the resource records to act upon.
*
*
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
*
*
* @param resourceRecords
* Information about the resource records to act upon.
*
* If you are creating an alias resource record set, omit ResourceRecords.
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withResourceRecords(java.util.Collection resourceRecords) {
setResourceRecords(resourceRecords);
return this;
}
/**
*
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted zone is
* unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*
*
* @param aliasTarget
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted
* zone is unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*/
public void setAliasTarget(AliasTarget aliasTarget) {
this.aliasTarget = aliasTarget;
}
/**
*
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted zone is
* unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*
*
* @return Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted
* zone is unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*/
public AliasTarget getAliasTarget() {
return this.aliasTarget;
}
/**
*
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted zone is
* unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
*
*
* @param aliasTarget
* Alias resource record sets only: Information about the CloudFront distribution, Elastic Beanstalk
* environment, ELB load balancer, Amazon S3 bucket, or Amazon Route 53 resource record set to which you are
* redirecting queries. The Elastic Beanstalk environment must have a regionalized subdomain.
*
* If you're creating resource records sets for a private hosted zone, note the following:
*
*
* -
*
* You can't create alias resource record sets for CloudFront distributions in a private hosted zone.
*
*
* -
*
* Creating geolocation alias resource record sets or latency alias resource record sets in a private hosted
* zone is unsupported.
*
*
* -
*
* For information about creating failover resource record sets in a private hosted zone, see Configuring Failover in a Private Hosted Zone in the Amazon Route 53 Developer Guide.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withAliasTarget(AliasTarget aliasTarget) {
setAliasTarget(aliasTarget);
return this;
}
/**
*
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a health
* check is passing, include the HealthCheckId element and specify the ID of the applicable health
* check.
*
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on the
* status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover resource
* record set, and you specify health check IDs for all of the resource record sets. If the health check for one
* resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops responding to queries using
* the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted alias,
* latency alias, geolocation alias, or failover alias resource record set, and you specify health check IDs for all
* of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for example, the
* endpoint specified by the IP address in the Value element. When you add a HealthCheckId
* element to a resource record set, Amazon Route 53 checks the health of the endpoint that you specified in the
* health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource record
* set for the larger, associated geographic region. For example, suppose you have resource record sets for a state
* in the United States, for the United States, for North America, and for all locations. If the endpoint for the
* state resource record set is unhealthy, Amazon Route 53 checks the resource record sets for the United States,
* for North America, and for all locations (a resource record set for which the value of CountryCode
* is *), in that order, until it finds a resource record set for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate health
* check for each endpoint. For example, create a health check for each HTTP server that is serving
* content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-1-www.example.com), not the name of the resource record
* sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and then associate the health check with those resource record sets,
* health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* @param healthCheckId
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a
* health check is passing, include the HealthCheckId element and specify the ID of the
* applicable health check.
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on
* the status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover
* resource record set, and you specify health check IDs for all of the resource record sets. If the health
* check for one resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops
* responding to queries using the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted
* alias, latency alias, geolocation alias, or failover alias resource record set, and you specify health
* check IDs for all of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for
* example, the endpoint specified by the IP address in the Value element. When you add a
* HealthCheckId element to a resource record set, Amazon Route 53 checks the health of the
* endpoint that you specified in the health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource
* record set for the larger, associated geographic region. For example, suppose you have resource record
* sets for a state in the United States, for the United States, for North America, and for all locations. If
* the endpoint for the state resource record set is unhealthy, Amazon Route 53 checks the resource record
* sets for the United States, for North America, and for all locations (a resource record set for which the
* value of CountryCode is *), in that order, until it finds a resource record set
* for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate
* health check for each endpoint. For example, create a health check for each HTTP server that
* is serving content for www.example.com. For the value of
* FullyQualifiedDomainName, specify the domain name of the server (such as
* us-east-1-www.example.com), not the name of the resource record sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and then associate the
* health check with those resource record sets, health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*/
public void setHealthCheckId(String healthCheckId) {
this.healthCheckId = healthCheckId;
}
/**
*
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a health
* check is passing, include the HealthCheckId element and specify the ID of the applicable health
* check.
*
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on the
* status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover resource
* record set, and you specify health check IDs for all of the resource record sets. If the health check for one
* resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops responding to queries using
* the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted alias,
* latency alias, geolocation alias, or failover alias resource record set, and you specify health check IDs for all
* of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for example, the
* endpoint specified by the IP address in the Value element. When you add a HealthCheckId
* element to a resource record set, Amazon Route 53 checks the health of the endpoint that you specified in the
* health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource record
* set for the larger, associated geographic region. For example, suppose you have resource record sets for a state
* in the United States, for the United States, for North America, and for all locations. If the endpoint for the
* state resource record set is unhealthy, Amazon Route 53 checks the resource record sets for the United States,
* for North America, and for all locations (a resource record set for which the value of CountryCode
* is *), in that order, until it finds a resource record set for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate health
* check for each endpoint. For example, create a health check for each HTTP server that is serving
* content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-1-www.example.com), not the name of the resource record
* sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and then associate the health check with those resource record sets,
* health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* @return If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a
* health check is passing, include the HealthCheckId element and specify the ID of the
* applicable health check.
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or
* more resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in
* part on the status of a health check. Configuring health checks only makes sense in the following
* configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover
* resource record set, and you specify health check IDs for all of the resource record sets. If the health
* check for one resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops
* responding to queries using the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted
* alias, latency alias, geolocation alias, or failover alias resource record set, and you specify health
* check IDs for all of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for
* example, the endpoint specified by the IP address in the Value element. When you add a
* HealthCheckId element to a resource record set, Amazon Route 53 checks the health of the
* endpoint that you specified in the health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource
* record set for the larger, associated geographic region. For example, suppose you have resource record
* sets for a state in the United States, for the United States, for North America, and for all locations.
* If the endpoint for the state resource record set is unhealthy, Amazon Route 53 checks the resource
* record sets for the United States, for North America, and for all locations (a resource record set for
* which the value of CountryCode is *), in that order, until it finds a resource
* record set for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate
* health check for each endpoint. For example, create a health check for each HTTP server that
* is serving content for www.example.com. For the value of
* FullyQualifiedDomainName, specify the domain name of the server (such as
* us-east-1-www.example.com), not the name of the resource record sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and then associate the
* health check with those resource record sets, health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*/
public String getHealthCheckId() {
return this.healthCheckId;
}
/**
*
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a health
* check is passing, include the HealthCheckId element and specify the ID of the applicable health
* check.
*
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on the
* status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover resource
* record set, and you specify health check IDs for all of the resource record sets. If the health check for one
* resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops responding to queries using
* the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted alias,
* latency alias, geolocation alias, or failover alias resource record set, and you specify health check IDs for all
* of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for example, the
* endpoint specified by the IP address in the Value element. When you add a HealthCheckId
* element to a resource record set, Amazon Route 53 checks the health of the endpoint that you specified in the
* health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource record
* set for the larger, associated geographic region. For example, suppose you have resource record sets for a state
* in the United States, for the United States, for North America, and for all locations. If the endpoint for the
* state resource record set is unhealthy, Amazon Route 53 checks the resource record sets for the United States,
* for North America, and for all locations (a resource record set for which the value of CountryCode
* is *), in that order, until it finds a resource record set for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate health
* check for each endpoint. For example, create a health check for each HTTP server that is serving
* content for www.example.com. For the value of FullyQualifiedDomainName, specify the
* domain name of the server (such as us-east-1-www.example.com), not the name of the resource record
* sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of FullyQualifiedDomainName
* matches the name of the resource record sets and then associate the health check with those resource record sets,
* health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
*
*
* @param healthCheckId
* If you want Amazon Route 53 to return this resource record set in response to a DNS query only when a
* health check is passing, include the HealthCheckId element and specify the ID of the
* applicable health check.
*
* Amazon Route 53 determines whether a resource record set is healthy based on one of the following:
*
*
* -
*
* By periodically sending a request to the endpoint that is specified in the health check
*
*
* -
*
* By aggregating the status of a specified group of health checks (calculated health checks)
*
*
* -
*
* By determining the current state of a CloudWatch alarm (CloudWatch metric health checks)
*
*
*
*
* For information about how Amazon Route 53 determines whether a health check is healthy, see
* CreateHealthCheck.
*
*
* The HealthCheckId element is only useful when Amazon Route 53 is choosing between two or more
* resource record sets to respond to a DNS query, and you want Amazon Route 53 to base the choice in part on
* the status of a health check. Configuring health checks only makes sense in the following configurations:
*
*
* -
*
* You're checking the health of the resource record sets in a weighted, latency, geolocation, or failover
* resource record set, and you specify health check IDs for all of the resource record sets. If the health
* check for one resource record set specifies an endpoint that is not healthy, Amazon Route 53 stops
* responding to queries using the value for that resource record set.
*
*
* -
*
* You set EvaluateTargetHealth to true for the resource record sets in an alias, weighted
* alias, latency alias, geolocation alias, or failover alias resource record set, and you specify health
* check IDs for all of the resource record sets that are referenced by the alias resource record sets.
*
*
*
*
*
* Amazon Route 53 doesn't check the health of the endpoint specified in the resource record set, for
* example, the endpoint specified by the IP address in the Value element. When you add a
* HealthCheckId element to a resource record set, Amazon Route 53 checks the health of the
* endpoint that you specified in the health check.
*
*
*
* For geolocation resource record sets, if an endpoint is unhealthy, Amazon Route 53 looks for a resource
* record set for the larger, associated geographic region. For example, suppose you have resource record
* sets for a state in the United States, for the United States, for North America, and for all locations. If
* the endpoint for the state resource record set is unhealthy, Amazon Route 53 checks the resource record
* sets for the United States, for North America, and for all locations (a resource record set for which the
* value of CountryCode is *), in that order, until it finds a resource record set
* for which the endpoint is healthy.
*
*
* If your health checks specify the endpoint only by domain name, we recommend that you create a separate
* health check for each endpoint. For example, create a health check for each HTTP server that
* is serving content for www.example.com. For the value of
* FullyQualifiedDomainName, specify the domain name of the server (such as
* us-east-1-www.example.com), not the name of the resource record sets (example.com).
*
*
*
* n this configuration, if you create a health check for which the value of
* FullyQualifiedDomainName matches the name of the resource record sets and then associate the
* health check with those resource record sets, health check results will be unpredictable.
*
*
*
* For more information, see the following topics in the Amazon Route 53 Developer Guide:
*
*
* -
*
*
* -
*
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withHealthCheckId(String healthCheckId) {
setHealthCheckId(healthCheckId);
return this;
}
/**
*
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created this
* resource record set for.
*
*
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set automatically. If
* you delete the resource record set by using ChangeResourceRecordSets, Amazon Route 53 doesn't
* automatically delete the traffic policy instance, and you'll continue to be charged for it even though it's no
* longer in use.
*
*
*
* @param trafficPolicyInstanceId
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created
* this resource record set for.
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set
* automatically. If you delete the resource record set by using ChangeResourceRecordSets,
* Amazon Route 53 doesn't automatically delete the traffic policy instance, and you'll continue to be
* charged for it even though it's no longer in use.
*
*/
public void setTrafficPolicyInstanceId(String trafficPolicyInstanceId) {
this.trafficPolicyInstanceId = trafficPolicyInstanceId;
}
/**
*
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created this
* resource record set for.
*
*
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set automatically. If
* you delete the resource record set by using ChangeResourceRecordSets, Amazon Route 53 doesn't
* automatically delete the traffic policy instance, and you'll continue to be charged for it even though it's no
* longer in use.
*
*
*
* @return When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53
* created this resource record set for.
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set
* automatically. If you delete the resource record set by using ChangeResourceRecordSets,
* Amazon Route 53 doesn't automatically delete the traffic policy instance, and you'll continue to be
* charged for it even though it's no longer in use.
*
*/
public String getTrafficPolicyInstanceId() {
return this.trafficPolicyInstanceId;
}
/**
*
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created this
* resource record set for.
*
*
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set automatically. If
* you delete the resource record set by using ChangeResourceRecordSets, Amazon Route 53 doesn't
* automatically delete the traffic policy instance, and you'll continue to be charged for it even though it's no
* longer in use.
*
*
*
* @param trafficPolicyInstanceId
* When you create a traffic policy instance, Amazon Route 53 automatically creates a resource record set.
* TrafficPolicyInstanceId is the ID of the traffic policy instance that Amazon Route 53 created
* this resource record set for.
*
* To delete the resource record set that is associated with a traffic policy instance, use
* DeleteTrafficPolicyInstance. Amazon Route 53 will delete the resource record set
* automatically. If you delete the resource record set by using ChangeResourceRecordSets,
* Amazon Route 53 doesn't automatically delete the traffic policy instance, and you'll continue to be
* charged for it even though it's no longer in use.
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ResourceRecordSet withTrafficPolicyInstanceId(String trafficPolicyInstanceId) {
setTrafficPolicyInstanceId(trafficPolicyInstanceId);
return this;
}
/**
* Returns a string representation of this object; useful for testing and debugging.
*
* @return A string representation of this object.
*
* @see java.lang.Object#toString()
*/
@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getName() != null)
sb.append("Name: " + getName() + ",");
if (getType() != null)
sb.append("Type: " + getType() + ",");
if (getSetIdentifier() != null)
sb.append("SetIdentifier: " + getSetIdentifier() + ",");
if (getWeight() != null)
sb.append("Weight: " + getWeight() + ",");
if (getRegion() != null)
sb.append("Region: " + getRegion() + ",");
if (getGeoLocation() != null)
sb.append("GeoLocation: " + getGeoLocation() + ",");
if (getFailover() != null)
sb.append("Failover: " + getFailover() + ",");
if (getTTL() != null)
sb.append("TTL: " + getTTL() + ",");
if (getResourceRecords() != null)
sb.append("ResourceRecords: " + getResourceRecords() + ",");
if (getAliasTarget() != null)
sb.append("AliasTarget: " + getAliasTarget() + ",");
if (getHealthCheckId() != null)
sb.append("HealthCheckId: " + getHealthCheckId() + ",");
if (getTrafficPolicyInstanceId() != null)
sb.append("TrafficPolicyInstanceId: " + getTrafficPolicyInstanceId());
sb.append("}");
return sb.toString();
}
@Override
public boolean equals(Object obj) {
if (this == obj)
return true;
if (obj == null)
return false;
if (obj instanceof ResourceRecordSet == false)
return false;
ResourceRecordSet other = (ResourceRecordSet) obj;
if (other.getName() == null ^ this.getName() == null)
return false;
if (other.getName() != null && other.getName().equals(this.getName()) == false)
return false;
if (other.getType() == null ^ this.getType() == null)
return false;
if (other.getType() != null && other.getType().equals(this.getType()) == false)
return false;
if (other.getSetIdentifier() == null ^ this.getSetIdentifier() == null)
return false;
if (other.getSetIdentifier() != null && other.getSetIdentifier().equals(this.getSetIdentifier()) == false)
return false;
if (other.getWeight() == null ^ this.getWeight() == null)
return false;
if (other.getWeight() != null && other.getWeight().equals(this.getWeight()) == false)
return false;
if (other.getRegion() == null ^ this.getRegion() == null)
return false;
if (other.getRegion() != null && other.getRegion().equals(this.getRegion()) == false)
return false;
if (other.getGeoLocation() == null ^ this.getGeoLocation() == null)
return false;
if (other.getGeoLocation() != null && other.getGeoLocation().equals(this.getGeoLocation()) == false)
return false;
if (other.getFailover() == null ^ this.getFailover() == null)
return false;
if (other.getFailover() != null && other.getFailover().equals(this.getFailover()) == false)
return false;
if (other.getTTL() == null ^ this.getTTL() == null)
return false;
if (other.getTTL() != null && other.getTTL().equals(this.getTTL()) == false)
return false;
if (other.getResourceRecords() == null ^ this.getResourceRecords() == null)
return false;
if (other.getResourceRecords() != null && other.getResourceRecords().equals(this.getResourceRecords()) == false)
return false;
if (other.getAliasTarget() == null ^ this.getAliasTarget() == null)
return false;
if (other.getAliasTarget() != null && other.getAliasTarget().equals(this.getAliasTarget()) == false)
return false;
if (other.getHealthCheckId() == null ^ this.getHealthCheckId() == null)
return false;
if (other.getHealthCheckId() != null && other.getHealthCheckId().equals(this.getHealthCheckId()) == false)
return false;
if (other.getTrafficPolicyInstanceId() == null ^ this.getTrafficPolicyInstanceId() == null)
return false;
if (other.getTrafficPolicyInstanceId() != null && other.getTrafficPolicyInstanceId().equals(this.getTrafficPolicyInstanceId()) == false)
return false;
return true;
}
@Override
public int hashCode() {
final int prime = 31;
int hashCode = 1;
hashCode = prime * hashCode + ((getName() == null) ? 0 : getName().hashCode());
hashCode = prime * hashCode + ((getType() == null) ? 0 : getType().hashCode());
hashCode = prime * hashCode + ((getSetIdentifier() == null) ? 0 : getSetIdentifier().hashCode());
hashCode = prime * hashCode + ((getWeight() == null) ? 0 : getWeight().hashCode());
hashCode = prime * hashCode + ((getRegion() == null) ? 0 : getRegion().hashCode());
hashCode = prime * hashCode + ((getGeoLocation() == null) ? 0 : getGeoLocation().hashCode());
hashCode = prime * hashCode + ((getFailover() == null) ? 0 : getFailover().hashCode());
hashCode = prime * hashCode + ((getTTL() == null) ? 0 : getTTL().hashCode());
hashCode = prime * hashCode + ((getResourceRecords() == null) ? 0 : getResourceRecords().hashCode());
hashCode = prime * hashCode + ((getAliasTarget() == null) ? 0 : getAliasTarget().hashCode());
hashCode = prime * hashCode + ((getHealthCheckId() == null) ? 0 : getHealthCheckId().hashCode());
hashCode = prime * hashCode + ((getTrafficPolicyInstanceId() == null) ? 0 : getTrafficPolicyInstanceId().hashCode());
return hashCode;
}
@Override
public ResourceRecordSet clone() {
try {
return (ResourceRecordSet) super.clone();
} catch (CloneNotSupportedException e) {
throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e);
}
}
}