blib/lib/Paws/Route53/ResourceRecordSet.pm

filter: Statementstmt 100% 17 / 17 Branchbran n/a Conditioncond n/a MC/DCmcdc n/a Subroutinesub 100% 1 / 1 Podpod n/a totaltotal 100% 18 / 18 CC 1 SCAR 0.0
CC
1
Cov
100%
BEGIN
1.0
CRAP 1.0
« blib/lib/Paws/Route53/ResourceRecord.pm ↑ Summary blib/lib/Paws/Route53/ResourceTagSet.pm »
1 # Generated by default/object.tt
2 package Paws::Route53::ResourceRecordSet;
3 2 ▶ use Moose;
Subroutine BEGIN: called CC=1 SCAR=0.0
4 2 has AliasTarget => (is => 'ro', isa => 'Paws::Route53::AliasTarget');
5 2 has Failover => (is => 'ro', isa => 'Str');
6 2 has GeoLocation => (is => 'ro', isa => 'Paws::Route53::GeoLocation');
7 2 has HealthCheckId => (is => 'ro', isa => 'Str');
8 2 has MultiValueAnswer => (is => 'ro', isa => 'Bool');
9 2 has Name => (is => 'ro', isa => 'Str', required => 1);
10 2 has Region => (is => 'ro', isa => 'Str');
11 2 has ResourceRecords => (is => 'ro', isa => 'ArrayRef[Paws::Route53::ResourceRecord]', request_name => 'ResourceRecord', traits => ['NameInRequest']);
12 2 has SetIdentifier => (is => 'ro', isa => 'Str');
13 2 has TrafficPolicyInstanceId => (is => 'ro', isa => 'Str');
14 2 has TTL => (is => 'ro', isa => 'Int');
15 2 has Type => (is => 'ro', isa => 'Str', required => 1);
16 2 has Weight => (is => 'ro', isa => 'Int');
17  
18 2 1;
19  
20 ### main pod documentation begin ###
21  
22 =head1 NAME
23  
24 Paws::Route53::ResourceRecordSet
25  
26 =head1 USAGE
27  
28 This class represents one of two things:
29  
30 =head3 Arguments in a call to a service
31  
32 Use the attributes of this class as arguments to methods. You shouldn't make instances of this class.
33 Each attribute should be used as a named argument in the calls that expect this type of object.
34  
35 As an example, if Att1 is expected to be a Paws::Route53::ResourceRecordSet object:
36  
37 $service_obj->Method(Att1 => { AliasTarget => $value, ..., Weight => $value });
38  
39 =head3 Results returned from an API call
40  
41 Use accessors for each attribute. If Att1 is expected to be an Paws::Route53::ResourceRecordSet object:
42  
43 $result = $service_obj->Method(...);
44 $result->Att1->AliasTarget
45  
46 =head1 DESCRIPTION
47  
48 Information about the resource record set to create or delete.
49  
50 =head1 ATTRIBUTES
51  
52  
53 =head2 AliasTarget => L<Paws::Route53::AliasTarget>
54  
55 I<Alias resource record sets only:> Information about the AWS resource,
56 such as a CloudFront distribution or an Amazon S3 bucket, that you want
57 to route traffic to.
58  
59 If you're creating resource records sets for a private hosted zone,
60 note the following:
61  
62 =over
63  
64 =item *
65  
66 You can't create an alias resource record set in a private hosted zone
67 to route traffic to a CloudFront distribution.
68  
69 =item *
70  
71 Creating geolocation alias resource record sets or latency alias
72 resource record sets in a private hosted zone is unsupported.
73  
74 =item *
75  
76 For information about creating failover resource record sets in a
77 private hosted zone, see Configuring Failover in a Private Hosted Zone
78 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-private-hosted-zones.html)
79 in the I<Amazon Route 53 Developer Guide>.
80  
81 =back
82  
83  
84  
85 =head2 Failover => Str
86  
87 I<Failover resource record sets only:> To configure failover, you add
88 the C<Failover> element to two resource record sets. For one resource
89 record set, you specify C<PRIMARY> as the value for C<Failover>; for
90 the other resource record set, you specify C<SECONDARY>. In addition,
91 you include the C<HealthCheckId> element and specify the health check
92 that you want Amazon Route 53 to perform for each resource record set.
93  
94 Except where noted, the following failover behaviors assume that you
95 have included the C<HealthCheckId> element in both resource record
96 sets:
97  
98 =over
99  
100 =item *
101  
102 When the primary resource record set is healthy, Route 53 responds to
103 DNS queries with the applicable value from the primary resource record
104 set regardless of the health of the secondary resource record set.
105  
106 =item *
107  
108 When the primary resource record set is unhealthy and the secondary
109 resource record set is healthy, Route 53 responds to DNS queries with
110 the applicable value from the secondary resource record set.
111  
112 =item *
113  
114 When the secondary resource record set is unhealthy, Route 53 responds
115 to DNS queries with the applicable value from the primary resource
116 record set regardless of the health of the primary resource record set.
117  
118 =item *
119  
120 If you omit the C<HealthCheckId> element for the secondary resource
121 record set, and if the primary resource record set is unhealthy, Route
122 53 always responds to DNS queries with the applicable value from the
123 secondary resource record set. This is true regardless of the health of
124 the associated endpoint.
125  
126 =back
127  
128 You can't create non-failover resource record sets that have the same
129 values for the C<Name> and C<Type> elements as failover resource record
130 sets.
131  
132 For failover alias resource record sets, you must also include the
133 C<EvaluateTargetHealth> element and set the value to true.
134  
135 For more information about configuring failover for Route 53, see the
136 following topics in the I<Amazon Route 53 Developer Guide>:
137  
138 =over
139  
140 =item *
141  
142 Route 53 Health Checks and DNS Failover
143 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html)
144  
145 =item *
146  
147 Configuring Failover in a Private Hosted Zone
148 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-private-hosted-zones.html)
149  
150 =back
151  
152  
153  
154 =head2 GeoLocation => L<Paws::Route53::GeoLocation>
155  
156 I<Geolocation resource record sets only:> A complex type that lets you
157 control how Amazon Route 53 responds to DNS queries based on the
158 geographic origin of the query. For example, if you want all queries
159 from Africa to be routed to a web server with an IP address of
160 C<192.0.2.111>, create a resource record set with a C<Type> of C<A> and
161 a C<ContinentCode> of C<AF>.
162  
163 Although creating geolocation and geolocation alias resource record
164 sets in a private hosted zone is allowed, it's not supported.
165  
166 If you create separate resource record sets for overlapping geographic
167 regions (for example, one resource record set for a continent and one
168 for a country on the same continent), priority goes to the smallest
169 geographic region. This allows you to route most queries for a
170 continent to one resource and to route queries for a country on that
171 continent to a different resource.
172  
173 You can't create two geolocation resource record sets that specify the
174 same geographic location.
175  
176 The value C<*> in the C<CountryCode> element matches all geographic
177 locations that aren't specified in other geolocation resource record
178 sets that have the same values for the C<Name> and C<Type> elements.
179  
180 Geolocation works by mapping IP addresses to locations. However, some
181 IP addresses aren't mapped to geographic locations, so even if you
182 create geolocation resource record sets that cover all seven
183 continents, Route 53 will receive some DNS queries from locations that
184 it can't identify. We recommend that you create a resource record set
185 for which the value of C<CountryCode> is C<*>. Two groups of queries
186 are routed to the resource that you specify in this record: queries
187 that come from locations for which you haven't created geolocation
188 resource record sets and queries from IP addresses that aren't mapped
189 to a location. If you don't create a C<*> resource record set, Route 53
190 returns a "no answer" response for queries from those locations.
191  
192 You can't create non-geolocation resource record sets that have the
193 same values for the C<Name> and C<Type> elements as geolocation
194 resource record sets.
195  
196  
197 =head2 HealthCheckId => Str
198  
199 If you want Amazon Route 53 to return this resource record set in
200 response to a DNS query only when the status of a health check is
201 healthy, include the C<HealthCheckId> element and specify the ID of the
202 applicable health check.
203  
204 Route 53 determines whether a resource record set is healthy based on
205 one of the following:
206  
207 =over
208  
209 =item *
210  
211 By periodically sending a request to the endpoint that is specified in
212 the health check
213  
214 =item *
215  
216 By aggregating the status of a specified group of health checks
217 (calculated health checks)
218  
219 =item *
220  
221 By determining the current state of a CloudWatch alarm (CloudWatch
222 metric health checks)
223  
224 =back
225  
226 Route 53 doesn't check the health of the endpoint that is specified in
227 the resource record set, for example, the endpoint specified by the IP
228 address in the C<Value> element. When you add a C<HealthCheckId>
229 element to a resource record set, Route 53 checks the health of the
230 endpoint that you specified in the health check.
231  
232 For more information, see the following topics in the I<Amazon Route 53
233 Developer Guide>:
234  
235 =over
236  
237 =item *
238  
239 How Amazon Route 53 Determines Whether an Endpoint Is Healthy
240 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-determining-health-of-endpoints.html)
241  
242 =item *
243  
244 Route 53 Health Checks and DNS Failover
245 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html)
246  
247 =item *
248  
249 Configuring Failover in a Private Hosted Zone
250 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-private-hosted-zones.html)
251  
252 =back
253  
254 B<When to Specify HealthCheckId>
255  
256 Specifying a value for C<HealthCheckId> is useful only when Route 53 is
257 choosing between two or more resource record sets to respond to a DNS
258 query, and you want Route 53 to base the choice in part on the status
259 of a health check. Configuring health checks makes sense only in the
260 following configurations:
261  
262 =over
263  
264 =item *
265  
266 B<Non-alias resource record sets>: You're checking the health of a
267 group of non-alias resource record sets that have the same routing
268 policy, name, and type (such as multiple weighted records named
269 www.example.com with a type of A) and you specify health check IDs for
270 all the resource record sets.
271  
272 If the health check status for a resource record set is healthy, Route
273 53 includes the record among the records that it responds to DNS
274 queries with.
275  
276 If the health check status for a resource record set is unhealthy,
277 Route 53 stops responding to DNS queries using the value for that
278 resource record set.
279  
280 If the health check status for all resource record sets in the group is
281 unhealthy, Route 53 considers all resource record sets in the group
282 healthy and responds to DNS queries accordingly.
283  
284 =item *
285  
286 B<Alias resource record sets>: You specify the following settings:
287  
288 =over
289  
290 =item *
291  
292 You set C<EvaluateTargetHealth> to true for an alias resource record
293 set in a group of resource record sets that have the same routing
294 policy, name, and type (such as multiple weighted records named
295 www.example.com with a type of A).
296  
297 =item *
298  
299 You configure the alias resource record set to route traffic to a
300 non-alias resource record set in the same hosted zone.
301  
302 =item *
303  
304 You specify a health check ID for the non-alias resource record set.
305  
306 =back
307  
308 If the health check status is healthy, Route 53 considers the alias
309 resource record set to be healthy and includes the alias record among
310 the records that it responds to DNS queries with.
311  
312 If the health check status is unhealthy, Route 53 stops responding to
313 DNS queries using the alias resource record set.
314  
315 The alias resource record set can also route traffic to a I<group> of
316 non-alias resource record sets that have the same routing policy, name,
317 and type. In that configuration, associate health checks with all of
318 the resource record sets in the group of non-alias resource record
319 sets.
320  
321 =back
322  
323 B<Geolocation Routing>
324  
325 For geolocation resource record sets, if an endpoint is unhealthy,
326 Route 53 looks for a resource record set for the larger, associated
327 geographic region. For example, suppose you have resource record sets
328 for a state in the United States, for the entire United States, for
329 North America, and a resource record set that has C<*> for
330 C<CountryCode> is C<*>, which applies to all locations. If the endpoint
331 for the state resource record set is unhealthy, Route 53 checks for
332 healthy resource record sets in the following order until it finds a
333 resource record set for which the endpoint is healthy:
334  
335 =over
336  
337 =item *
338  
339 The United States
340  
341 =item *
342  
343 North America
344  
345 =item *
346  
347 The default resource record set
348  
349 =back
350  
351 B<Specifying the Health Check Endpoint by Domain Name>
352  
353 If your health checks specify the endpoint only by domain name, we
354 recommend that you create a separate health check for each endpoint.
355 For example, create a health check for each C<HTTP> server that is
356 serving content for C<www.example.com>. For the value of
357 C<FullyQualifiedDomainName>, specify the domain name of the server
358 (such as C<us-east-2-www.example.com>), not the name of the resource
359 record sets (C<www.example.com>).
360  
361 Health check results will be unpredictable if you do the following:
362  
363 =over
364  
365 =item *
366  
367 Create a health check that has the same value for
368 C<FullyQualifiedDomainName> as the name of a resource record set.
369  
370 =item *
371  
372 Associate that health check with the resource record set.
373  
374 =back
375  
376  
377  
378 =head2 MultiValueAnswer => Bool
379  
380 I<Multivalue answer resource record sets only>: To route traffic
381 approximately randomly to multiple resources, such as web servers,
382 create one multivalue answer record for each resource and specify
383 C<true> for C<MultiValueAnswer>. Note the following:
384  
385 =over
386  
387 =item *
388  
389 If you associate a health check with a multivalue answer resource
390 record set, Amazon Route 53 responds to DNS queries with the
391 corresponding IP address only when the health check is healthy.
392  
393 =item *
394  
395 If you don't associate a health check with a multivalue answer record,
396 Route 53 always considers the record to be healthy.
397  
398 =item *
399  
400 Route 53 responds to DNS queries with up to eight healthy records; if
401 you have eight or fewer healthy records, Route 53 responds to all DNS
402 queries with all the healthy records.
403  
404 =item *
405  
406 If you have more than eight healthy records, Route 53 responds to
407 different DNS resolvers with different combinations of healthy records.
408  
409 =item *
410  
411 When all records are unhealthy, Route 53 responds to DNS queries with
412 up to eight unhealthy records.
413  
414 =item *
415  
416 If a resource becomes unavailable after a resolver caches a response,
417 client software typically tries another of the IP addresses in the
418 response.
419  
420 =back
421  
422 You can't create multivalue answer alias records.
423  
424  
425 =head2 B<REQUIRED> Name => Str
426  
427 For C<ChangeResourceRecordSets> requests, the name of the record that
428 you want to create, update, or delete. For C<ListResourceRecordSets>
429 responses, the name of a record in the specified hosted zone.
430  
431 B<ChangeResourceRecordSets Only>
432  
433 Enter a fully qualified domain name, for example, C<www.example.com>.
434 You can optionally include a trailing dot. If you omit the trailing
435 dot, Amazon Route 53 assumes that the domain name that you specify is
436 fully qualified. This means that Route 53 treats C<www.example.com>
437 (without a trailing dot) and C<www.example.com.> (with a trailing dot)
438 as identical.
439  
440 For information about how to specify characters other than C<a-z>,
441 C<0-9>, and C<-> (hyphen) and how to specify internationalized domain
442 names, see DNS Domain Name Format
443 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DomainNameFormat.html)
444 in the I<Amazon Route 53 Developer Guide>.
445  
446 You can use the asterisk (*) wildcard to replace the leftmost label in
447 a domain name, for example, C<*.example.com>. Note the following:
448  
449 =over
450  
451 =item *
452  
453 The * must replace the entire label. For example, you can't specify
454 C<*prod.example.com> or C<prod*.example.com>.
455  
456 =item *
457  
458 The * can't replace any of the middle labels, for example,
459 marketing.*.example.com.
460  
461 =item *
462  
463 If you include * in any position other than the leftmost label in a
464 domain name, DNS treats it as an * character (ASCII 42), not as a
465 wildcard.
466  
467 You can't use the * wildcard for resource records sets that have a type
468 of NS.
469  
470 =back
471  
472 You can use the * wildcard as the leftmost label in a domain name, for
473 example, C<*.example.com>. You can't use an * for one of the middle
474 labels, for example, C<marketing.*.example.com>. In addition, the *
475 must replace the entire label; for example, you can't specify
476 C<prod*.example.com>.
477  
478  
479 =head2 Region => Str
480  
481 I<Latency-based resource record sets only:> The Amazon EC2 Region where
482 you created the resource that this resource record set refers to. The
483 resource typically is an AWS resource, such as an EC2 instance or an
484 ELB load balancer, and is referred to by an IP address or a DNS domain
485 name, depending on the record type.
486  
487 Although creating latency and latency alias resource record sets in a
488 private hosted zone is allowed, it's not supported.
489  
490 When Amazon Route 53 receives a DNS query for a domain name and type
491 for which you have created latency resource record sets, Route 53
492 selects the latency resource record set that has the lowest latency
493 between the end user and the associated Amazon EC2 Region. Route 53
494 then returns the value that is associated with the selected resource
495 record set.
496  
497 Note the following:
498  
499 =over
500  
501 =item *
502  
503 You can only specify one C<ResourceRecord> per latency resource record
504 set.
505  
506 =item *
507  
508 You can only create one latency resource record set for each Amazon EC2
509 Region.
510  
511 =item *
512  
513 You aren't required to create latency resource record sets for all
514 Amazon EC2 Regions. Route 53 will choose the region with the best
515 latency from among the regions that you create latency resource record
516 sets for.
517  
518 =item *
519  
520 You can't create non-latency resource record sets that have the same
521 values for the C<Name> and C<Type> elements as latency resource record
522 sets.
523  
524 =back
525  
526  
527  
528 =head2 ResourceRecords => ArrayRef[L<Paws::Route53::ResourceRecord>]
529  
530 Information about the resource records to act upon.
531  
532 If you're creating an alias resource record set, omit
533 C<ResourceRecords>.
534  
535  
536 =head2 SetIdentifier => Str
537  
538 I<Resource record sets that have a routing policy other than simple:>
539 An identifier that differentiates among multiple resource record sets
540 that have the same combination of name and type, such as multiple
541 weighted resource record sets named acme.example.com that have a type
542 of A. In a group of resource record sets that have the same name and
543 type, the value of C<SetIdentifier> must be unique for each resource
544 record set.
545  
546 For information about routing policies, see Choosing a Routing Policy
547 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html)
548 in the I<Amazon Route 53 Developer Guide>.
549  
550  
551 =head2 TrafficPolicyInstanceId => Str
552  
553 When you create a traffic policy instance, Amazon Route 53
554 automatically creates a resource record set. C<TrafficPolicyInstanceId>
555 is the ID of the traffic policy instance that Route 53 created this
556 resource record set for.
557  
558 To delete the resource record set that is associated with a traffic
559 policy instance, use C<DeleteTrafficPolicyInstance>. Route 53 will
560 delete the resource record set automatically. If you delete the
561 resource record set by using C<ChangeResourceRecordSets>, Route 53
562 doesn't automatically delete the traffic policy instance, and you'll
563 continue to be charged for it even though it's no longer in use.
564  
565  
566 =head2 TTL => Int
567  
568 The resource record cache time to live (TTL), in seconds. Note the
569 following:
570  
571 =over
572  
573 =item *
574  
575 If you're creating or updating an alias resource record set, omit
576 C<TTL>. Amazon Route 53 uses the value of C<TTL> for the alias target.
577  
578 =item *
579  
580 If you're associating this resource record set with a health check (if
581 you're adding a C<HealthCheckId> element), we recommend that you
582 specify a C<TTL> of 60 seconds or less so clients respond quickly to
583 changes in health status.
584  
585 =item *
586  
587 All of the resource record sets in a group of weighted resource record
588 sets must have the same value for C<TTL>.
589  
590 =item *
591  
592 If a group of weighted resource record sets includes one or more
593 weighted alias resource record sets for which the alias target is an
594 ELB load balancer, we recommend that you specify a C<TTL> of 60 seconds
595 for all of the non-alias weighted resource record sets that have the
596 same name and type. Values other than 60 seconds (the TTL for load
597 balancers) will change the effect of the values that you specify for
598 C<Weight>.
599  
600 =back
601  
602  
603  
604 =head2 B<REQUIRED> Type => Str
605  
606 The DNS record type. For information about different record types and
607 how data is encoded for them, see Supported DNS Resource Record Types
608 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html)
609 in the I<Amazon Route 53 Developer Guide>.
610  
611 Valid values for basic resource record sets: C<A> | C<AAAA> | C<CAA> |
612 C<CNAME> | C<DS> |C<MX> | C<NAPTR> | C<NS> | C<PTR> | C<SOA> | C<SPF> |
613 C<SRV> | C<TXT>
614  
615 Values for weighted, latency, geolocation, and failover resource record
616 sets: C<A> | C<AAAA> | C<CAA> | C<CNAME> | C<MX> | C<NAPTR> | C<PTR> |
617 C<SPF> | C<SRV> | C<TXT>. When creating a group of weighted, latency,
618 geolocation, or failover resource record sets, specify the same value
619 for all of the resource record sets in the group.
620  
621 Valid values for multivalue answer resource record sets: C<A> | C<AAAA>
622 | C<MX> | C<NAPTR> | C<PTR> | C<SPF> | C<SRV> | C<TXT>
623  
624 SPF records were formerly used to verify the identity of the sender of
625 email messages. However, we no longer recommend that you create
626 resource record sets for which the value of C<Type> is C<SPF>. RFC
627 7208, I<Sender Policy Framework (SPF) for Authorizing Use of Domains in
628 Email, Version 1>, has been updated to say, "...[I]ts existence and
629 mechanism defined in [RFC4408] have led to some interoperability
630 issues. Accordingly, its use is no longer appropriate for SPF version
631 1; implementations are not to use it." In RFC 7208, see section 14.1,
632 The SPF DNS Record Type
633 (http://tools.ietf.org/html/rfc7208#section-14.1).
634  
635 Values for alias resource record sets:
636  
637 =over
638  
639 =item *
640  
641 B<Amazon API Gateway custom regional APIs and edge-optimized APIs:>
642 C<A>
643  
644 =item *
645  
646 B<CloudFront distributions:> C<A>
647  
648 If IPv6 is enabled for the distribution, create two resource record
649 sets to route traffic to your distribution, one with a value of C<A>
650 and one with a value of C<AAAA>.
651  
652 =item *
653  
654 B<Amazon API Gateway environment that has a regionalized subdomain>:
655 C<A>
656  
657 =item *
658  
659 B<ELB load balancers:> C<A> | C<AAAA>
660  
661 =item *
662  
663 B<Amazon S3 buckets:> C<A>
664  
665 =item *
666  
667 B<Amazon Virtual Private Cloud interface VPC endpoints> C<A>
668  
669 =item *
670  
671 B<Another resource record set in this hosted zone:> Specify the type of
672 the resource record set that you're creating the alias for. All values
673 are supported except C<NS> and C<SOA>.
674  
675 If you're creating an alias record that has the same name as the hosted
676 zone (known as the zone apex), you can't route traffic to a record for
677 which the value of C<Type> is C<CNAME>. This is because the alias
678 record must have the same type as the record you're routing traffic to,
679 and creating a CNAME record for the zone apex isn't supported even for
680 an alias record.
681  
682 =back
683  
684  
685  
686 =head2 Weight => Int
687  
688 I<Weighted resource record sets only:> Among resource record sets that
689 have the same combination of DNS name and type, a value that determines
690 the proportion of DNS queries that Amazon Route 53 responds to using
691 the current resource record set. Route 53 calculates the sum of the
692 weights for the resource record sets that have the same combination of
693 DNS name and type. Route 53 then responds to queries based on the ratio
694 of a resource's weight to the total. Note the following:
695  
696 =over
697  
698 =item *
699  
700 You must specify a value for the C<Weight> element for every weighted
701 resource record set.
702  
703 =item *
704  
705 You can only specify one C<ResourceRecord> per weighted resource record
706 set.
707  
708 =item *
709  
710 You can't create latency, failover, or geolocation resource record sets
711 that have the same values for the C<Name> and C<Type> elements as
712 weighted resource record sets.
713  
714 =item *
715  
716 You can create a maximum of 100 weighted resource record sets that have
717 the same values for the C<Name> and C<Type> elements.
718  
719 =item *
720  
721 For weighted (but not weighted alias) resource record sets, if you set
722 C<Weight> to C<0> for a resource record set, Route 53 never responds to
723 queries with the applicable value for that resource record set.
724 However, if you set C<Weight> to C<0> for all resource record sets that
725 have the same combination of DNS name and type, traffic is routed to
726 all resources with equal probability.
727  
728 The effect of setting C<Weight> to C<0> is different when you associate
729 health checks with weighted resource record sets. For more information,
730 see Options for Configuring Route 53 Active-Active and Active-Passive
731 Failover
732 (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-configuring-options.html)
733 in the I<Amazon Route 53 Developer Guide>.
734  
735 =back
736  
737  
738  
739  
740 =head1 SEE ALSO
741  
742 This class forms part of L<Paws>, describing an object used in L<Paws::Route53>
743  
744 =head1 BUGS and CONTRIBUTIONS
745  
746 The source code is located here: L<https://github.com/pplu/aws-sdk-perl>
747  
748 Please report bugs to: L<https://github.com/pplu/aws-sdk-perl/issues>
749  
750 =cut
751  
« blib/lib/Paws/Route53/ResourceRecord.pm ↑ Summary blib/lib/Paws/Route53/ResourceTagSet.pm »