NsRecordProps

class aws_cdk.aws_route53.NsRecordProps(*, zone, comment=None, delete_existing=None, geo_location=None, record_name=None, ttl=None, values)

Bases: RecordSetOptions

Construction properties for a NSRecord.

Parameters:

zone (IHostedZone) – The hosted zone in which to define the new record.
comment (Optional[str]) – A comment to add on the record. Default: no comment
delete_existing (Optional[bool]) – Whether to delete the same record set in the hosted zone if it already exists (dangerous!). This allows to deploy a new record set while minimizing the downtime because the new record set will be created immediately after the existing one is deleted. It also avoids “manual” actions to delete existing record sets. .. epigraph:: N.B.: this feature is dangerous, use with caution! It can only be used safely when deleteExisting is set to true as soon as the resource is added to the stack. Changing an existing Record Set’s deleteExisting property from false -> true after deployment will delete the record! Default: false
geo_location (Optional[GeoLocation]) – The geographical origin for this record to return DNS records based on the user’s location.
record_name (Optional[str]) – The subdomain name for this record. This should be relative to the zone root name. For example, if you want to create a record for acme.example.com, specify “acme”. You can also specify the fully qualified domain name which terminates with a “.”. For example, “acme.example.com.”. Default: zone root
ttl (Optional[Duration]) – The resource record cache time to live (TTL). Default: Duration.minutes(30)
values (Sequence[str]) – The NS values.

ExampleMetadata:

infused

Example:

# my_zone: route53.HostedZone


route53.NsRecord(self, "NSRecord",
    zone=my_zone,
    record_name="foo",
    values=["ns-1.awsdns.co.uk.", "ns-2.awsdns.com."
    ],
    ttl=Duration.minutes(90)
)

Attributes

comment

A comment to add on the record.

Default:: no comment

delete_existing

Whether to delete the same record set in the hosted zone if it already exists (dangerous!).

This allows to deploy a new record set while minimizing the downtime because the new record set will be created immediately after the existing one is deleted. It also avoids “manual” actions to delete existing record sets. .. epigraph:

**N.B.:** this feature is dangerous, use with caution! It can only be used safely when
``deleteExisting`` is set to ``true`` as soon as the resource is added to the stack. Changing
an existing Record Set's ``deleteExisting`` property from ``false -> true`` after deployment
will delete the record!

Default:: false

geo_location: The geographical origin for this record to return DNS records based on the user’s location.

record_name

The subdomain name for this record. This should be relative to the zone root name.

For example, if you want to create a record for acme.example.com, specify “acme”.

You can also specify the fully qualified domain name which terminates with a “.”. For example, “acme.example.com.”.

Default:: zone root

ttl

The resource record cache time to live (TTL).

Default:: Duration.minutes(30)

values: The NS values.

zone: The hosted zone in which to define the new record.