4.4.2. ARecord¶

class dyn.tm.records.ARecord(zone, fqdn, *args, **kwargs)[source]¶

The IPv4 Address (A) Record forward maps a host name to an IPv4 address.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an ARecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added address – IPv4 address for the record ttl – TTL for this record

address¶: Return the value of this record’s address property

rdata()[source]¶: Return this ARecord‘s rdata as a JSON blob

4.4.3. AAAARecord¶

class dyn.tm.records.AAAARecord(zone, fqdn, *args, **kwargs)[source]¶

The IPv6 Address (AAAA) Record is used to forward map hosts to IPv6 addresses and is the current IETF recommendation for this purpose.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an AAAARecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added address – IPv6 address for the record ttl – TTL for this record

address¶: Return the value of this record’s address property

rdata()[source]¶: Return this AAAARecord‘s rdata as a JSON blob

4.4.4. ALIASRecord¶

class dyn.tm.records.ALIASRecord(zone, fqdn, *args, **kwargs)[source]¶

The ALIAS Records map an alias (CNAME) to the real or canonical name that may lie inside or outside the current zone.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an ALIASRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added alias – Hostname ttl – TTL for this record

alias¶: Hostname

rdata()[source]¶: Return this ALIASRecord‘s rdata as a JSON blob

4.4.5. CERTRecord¶

class dyn.tm.records.CERTRecord(zone, fqdn, *args, **kwargs)[source]¶

The Certificate (CERT) Record may be used to store either public key certificates or Certificate Revocation Lists (CRL) in the zone file.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a CERTRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added format – Numeric value for the certificate type tag – Numeric value for the public key certificate algorithm – Public key algorithm number used to generate the certificate certificate – The public key certificate ttl – TTL for this record in seconds

algorithm¶: Public key algorithm number used to generate the certificate

certificate¶: The public key certificate

format¶: Numeric value for the certificate type.

rdata()[source]¶: Return this CERTRecord‘s rdata as a JSON blob

tag¶: Numeric value for the public key certificate

4.4.6. CDNSKEYRecord¶

class dyn.tm.records.CDNSKEYRecord(zone, fqdn, *args, **kwargs)[source]¶

The CDNSKEY Record, or “Child DNSKEY”, describes the public key of a public key (asymmetric) cryptographic algorithm used with DNSSEC.nis. This is the DNSKEY for a Child Zone

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a DNSKEYRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
protocol – Numeric value for protocol
public_key – The public key for the DNSSEC signed zone
algorithm – Numeric value representing the public key encryption algorithm which will sign the zone. Must be one of 1 (RSA-MD5), 2 (Diffie-Hellman), 3 (DSA/SHA-1), 4 (Elliptic Curve), or 5 (RSA-SHA-1)
flags – Numeric value confirming this is the zone’s DNSKEY
ttl – TTL for this record. Use 0 for zone default

algorithm¶: Public key encryption algorithm will sign the zone

flags¶: Numeric value confirming this is the zone’s DNSKEY

protocol¶: Numeric value for protocol. Set to 3 for DNSSEC

public_key¶: The public key for the DNSSEC signed zone

rdata()[source]¶: Return this DNSKEYRecord‘s rdata as a JSON blob

4.4.7. CSYNCRecord¶

class dyn.tm.records.CSYNCRecord(zone, fqdn, *args, **kwargs)[source]¶

The CSYNC RRType contains, in its RDATA component, these parts: an SOA serial number, a set of flags, and a simple bit-list indicating the DNS RRTypes in the child that should be processed by the parental agent in order to modify the DNS delegation records within the parent’s zone for the child DNS operator.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a DSRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added soa_serial – SOA serial to bind to this record. flags – list of flags (‘soaminimum’, ‘immediate’) rectypes – list of record types to bind to this record. ttl – TTL for this record

flags¶: The flags, in list form

rdata()[source]¶: Return this DSRecord‘s rdata as a JSON blob

rectypes¶: list of record types

soa_serial¶: SOA Serial

4.4.8. CDSRecord¶

class dyn.tm.records.CDSRecord(zone, fqdn, *args, **kwargs)[source]¶

The Child Delegation Signer (CDS) record type is used in DNSSEC to create the chain of trust or authority from a signed child zone to a signed parent zone.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a DSRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
digest – The digest in hexadecimal form. 20-byte, hexadecimal-encoded, one-way hash of the DNSKEY record surrounded by parenthesis characters ‘(‘ & ‘)’
keytag – The digest mechanism to use to verify the digest
algorithm – Numeric value representing the public key encryption algorithm which will sign the zone. Must be one of 1 (RSA-MD5), 2 (Diffie-Hellman), 3 (DSA/SHA-1), 4 (Elliptic Curve), or 5 (RSA-SHA-1)
digtype – the digest mechanism to use to verify the digest. Valid values are SHA1, SHA256
ttl – TTL for this record. Use 0 for zone default

algorithm¶: Identifies the encoding algorithm

digest¶: The digest in hexadecimal form. 20-byte, hexadecimal-encoded, one-way hash of the DNSKEY record surrounded by parenthesis characters

digtype¶: Identifies which digest mechanism to use to verify the digest

keytag¶: Identifies which digest mechanism to use to verify the digest

rdata()[source]¶: Return this DSRecord‘s rdata as a JSON blob

4.4.9. CNAMERecord¶

class dyn.tm.records.CNAMERecord(zone, fqdn, *args, **kwargs)[source]¶

The Canonical Name (CNAME) Records map an alias to the real or canonical name that may lie inside or outside the current zone.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an CNAMERecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added cname – Hostname ttl – TTL for this record

cname¶: Hostname

rdata()[source]¶: Return this CNAMERecord‘s rdata as a JSON blob

4.4.10. DHCIDRecord¶

class dyn.tm.records.DHCIDRecord(zone, fqdn, *args, **kwargs)[source]¶

The DHCIDRecord provides a means by which DHCP clients or servers can associate a DHCP client’s identity with a DNS name, so that multiple DHCP clients and servers may deterministically perform dynamic DNS updates to the same zone.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an DHCIDRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added digest – Base-64 encoded digest of DHCP data ttl – TTL for this record

digest¶: Base-64 encoded digest of DHCP data

rdata()[source]¶: Return this DHCIDRecord‘s rdata as a JSON blob

4.4.11. DNAMERecord¶

class dyn.tm.records.DNAMERecord(zone, fqdn, *args, **kwargs)[source]¶

The Delegation of Reverse Name (DNAME) Record is designed to assist the delegation of reverse mapping by reducing the size of the data that must be entered. DNAME’s are designed to be used in conjunction with a bit label but do not strictly require one. However, do note that without a bit label a DNAME is equivalent to a CNAME when used in a reverse-map zone file.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an DNAMERecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added dname – Target Hostname ttl – TTL for this record

dname¶: Target hostname

rdata()[source]¶: Return this DNAMERecord‘s rdata as a JSON blob

4.4.12. DNSKEYRecord¶

class dyn.tm.records.DNSKEYRecord(zone, fqdn, *args, **kwargs)[source]¶

The DNSKEY Record describes the public key of a public key (asymmetric) cryptographic algorithm used with DNSSEC.nis. It is typically used to authenticate signed keys or zones.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a DNSKEYRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
protocol – Numeric value for protocol
public_key – The public key for the DNSSEC signed zone
algorithm – Numeric value representing the public key encryption algorithm which will sign the zone. Must be one of 1 (RSA-MD5), 2 (Diffie-Hellman), 3 (DSA/SHA-1), 4 (Elliptic Curve), or 5 (RSA-SHA-1)
flags – Numeric value confirming this is the zone’s DNSKEY
ttl – TTL for this record. Use 0 for zone default

algorithm¶: Public key encryption algorithm will sign the zone

flags¶: Numeric value confirming this is the zone’s DNSKEY

protocol¶: Numeric value for protocol. Set to 3 for DNSSEC

public_key¶: The public key for the DNSSEC signed zone

rdata()[source]¶: Return this DNSKEYRecord‘s rdata as a JSON blob

4.4.13. DSRecord¶

class dyn.tm.records.DSRecord(zone, fqdn, *args, **kwargs)[source]¶

The Delegation Signer (DS) record type is used in DNSSEC to create the chain of trust or authority from a signed parent zone to a signed child zone.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a DSRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
digest – The digest in hexadecimal form. 20-byte, hexadecimal-encoded, one-way hash of the DNSKEY record surrounded by parenthesis characters ‘(‘ & ‘)’
keytag – The digest mechanism to use to verify the digest
algorithm – Numeric value representing the public key encryption algorithm which will sign the zone. Must be one of 1 (RSA-MD5), 2 (Diffie-Hellman), 3 (DSA/SHA-1), 4 (Elliptic Curve), or 5 (RSA-SHA-1)
digtype – the digest mechanism to use to verify the digest. Valid values are SHA1, SHA256
ttl – TTL for this record. Use 0 for zone default

algorithm¶: Identifies the encoding algorithm

digest¶: The digest in hexadecimal form. 20-byte, hexadecimal-encoded, one-way hash of the DNSKEY record surrounded by parenthesis characters

digtype¶: Identifies which digest mechanism to use to verify the digest

keytag¶: Identifies which digest mechanism to use to verify the digest

rdata()[source]¶: Return this DSRecord‘s rdata as a JSON blob

4.4.14. KEYRecord¶

class dyn.tm.records.KEYRecord(zone, fqdn, *args, **kwargs)[source]¶

“Public Key” (KEY) Records are used for the storage of public keys for use by multiple applications such as IPSec, SSH, etc..., as well as for use by DNS security methods including the original DNSSEC protocol. However, as of RFC3445 the use of KEYRecord‘s have been limited to use in DNS Security operations such as DDNS and zone transfer due to the difficulty of querying for specific uses.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a KEYRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
algorithm – Numeric value representing the public key encryption algorithm which will sign the zone. Must be one of 1 (RSA-MD5), 2 (Diffie-Hellman), 3 (DSA/SHA-1), 4 (Elliptic Curve), or 5 (RSA-SHA-1)
flags – See RFC 2535 for information on KEY record flags
protocol – Numeric identifier of the protocol for this KEY record
public_key – The public key for this record
ttl – TTL for the record in seconds

algorithm¶: Numeric identifier for algorithm used

flags¶: See RFC 2535 for information about Key record flags

protocol¶: Numeric identifier of the protocol for this KEY record

public_key¶: The public key for this record

rdata()[source]¶: Return this KEYRecord‘s rdata as a JSON blob

4.4.15. KXRecord¶

class dyn.tm.records.KXRecord(zone, fqdn, *args, **kwargs)[source]¶

The “Key Exchanger” (KX) Record type is provided with one or more alternative hosts.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a KXRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
exchange – Hostname that will act as the Key Exchanger. The hostname must have a CNAMERecord, an ARecord and/or an AAAARecord associated with it
preference – Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node
ttl – TTL for the record in seconds

exchange¶: Hostname that will act as the Key Exchanger. The hostname must have a CNAME record, an A Record and/or an AAAA record associated with it

preference¶: Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node

rdata()[source]¶: Return this KXRecord‘s rdata as a JSON blob

4.4.16. LOCRecord¶

class dyn.tm.records.LOCRecord(zone, fqdn, *args, **kwargs)[source]¶

LOCRecord‘s allow for the definition of geographic positioning information associated with a host or service name.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a LOCRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
altitude – Measured in meters above sea level
horiz_pre –
latitude – Measured in degrees, minutes, and seconds with N/S indicator for North and South
longitude – Measured in degrees, minutes, and seconds with E/W indicator for East and West
size –
version –
vert_pre –
ttl – TTL for the record in seconds

altitude¶: Measured in meters above sea level

horiz_pre¶: Defaults to 10,000 meters

latitude¶: Measured in degrees, minutes, and seconds with N/S indicator for North and South. Example: 45 24 15 N, where 45 = degrees, 24 = minutes, 15 = seconds

longitude¶: Measured in degrees, minutes, and seconds with E/W indicator for East and West. Example 89 23 18 W, where 89 = degrees, 23 = minutes, 18 = seconds

rdata()[source]¶: Return this LOCRecord‘s rdata as a JSON blob

size¶: Defaults to 1 meter

version¶: Number of the representation. Must be zero (0) NOTE: Version has no setter, because it will never not be 0

vert_pre¶

4.4.17. IPSECKEYRecord¶

class dyn.tm.records.IPSECKEYRecord(zone, fqdn, *args, **kwargs)[source]¶

The IPSECKEY is used for storage of keys used specifically for IPSec oerations

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an IPSECKEYRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
precedence – Indicates priority among multiple IPSECKEYS. Lower numbers are higher priority
gatetype – Gateway type. Must be one of 0, 1, 2, or 3
algorithm – Public key’s cryptographic algorithm and format. Must be one of 0, 1, or 2
gateway – Gateway used to create IPsec tunnel. Based on Gateway type
public_key – Base64 encoding of the public key. Whitespace is allowed
ttl – TTL for the record in seconds

algorithm¶: Public key’s cryptographic algorithm and format

gatetype¶: Gateway type. Must be one of 0, 1, 2, or 3

gateway¶: Gateway used to create IPsec tunnel. Based on Gateway type

precedence¶: Indicates priority among multiple IPSECKEYS. Lower numbers are higher priority

public_key¶: Base64 encoding of the public key. Whitespace is allowed

rdata()[source]¶: Return this IPSECKEYRecord‘s rdata as a JSON blob

4.4.18. MXRecord¶

class dyn.tm.records.MXRecord(zone, fqdn, *args, **kwargs)[source]¶

The “Mail Exchanger” record type specifies the name and relative preference of mail servers for a Zone. Defined in RFC 1035

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an MXRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
exchange – Hostname of the server responsible for accepting mail messages in the zone
preference – Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node.
ttl – TTL for the record in seconds

exchange¶: Hostname of the server responsible for accepting mail messages in the zone

preference¶: Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node

rdata()[source]¶: Return this MXRecord‘s rdata as a JSON blob

4.4.19. NAPTRRecord¶

class dyn.tm.records.NAPTRRecord(zone, fqdn, *args, **kwargs)[source]¶

Naming Authority Pointer Records are a part of the Dynamic Delegation Discovery System (DDDS). The NAPTR is a generic record that defines a rule that may be applied to private data owned by a client application.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an NAPTRRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
order – Indicates the required priority for processing NAPTR records. Lowest value is used first.
preference – Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.
services – Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTRRecord points.
regexp – The NAPTR record accepts regular expressions
replacement – The next domain name to find. Only applies if this NAPTRRecord is non-terminal.
flags – Should be the letter “U”. This indicates that this NAPTR record terminal
ttl – TTL for the record in seconds

flags¶: Should be the letter “U”. This indicates that this NAPTR record terminal (E.164 number that maps directly to a URI)

order¶: Indicates the required priority for processing NAPTR records. Lowest value is used first

preference¶: Indicates priority where two or more NAPTR records have identical order values. Lowest value is used first.

rdata()[source]¶: Return this NAPTRRecord‘s rdata as a JSON blob

regexp¶: The NAPTR record accepts regular expressions

replacement¶: The next domain name to find. Only applies if this NAPTR record is non-terminal

services¶: Always starts with “e2u+” (E.164 to URI). After the e2u+ there is a string that defines the type and optionally the subtype of the URI where this NAPTR record points

4.4.20. PTRRecord¶

class dyn.tm.records.PTRRecord(zone, fqdn, *args, **kwargs)[source]¶

Pointer Records are used to reverse map an IPv4 or IPv6 IP address to a host name

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a PTRRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added ptrdname – The hostname where the IP address should be directed ttl – TTL for the record in seconds

ptrdname¶: Hostname where the IP address should be directed

rdata()[source]¶: Return this PTRRecord‘s rdata as a JSON blob

4.4.21. PXRecord¶

class dyn.tm.records.PXRecord(zone, fqdn, *args, **kwargs)[source]¶

The X.400 to RFC 822 E-mail RR allows mapping of ITU X.400 format e-mail addresses to RFC 822 format e-mail addresses using a MIXER-conformant gateway.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an PXRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added preference – Sets priority for processing records of the same type. Lowest value is processed first. map822 – mail hostname mapx400 – The domain name derived from the X.400 part of MCGAM ttl – TTL for the record in seconds

map822¶: mail hostname

mapx400¶: Enter the domain name derived from the X.400 part of MCGAM

preference¶: Sets priority for processing records of the same type. Lowest value is processed first

rdata()[source]¶: Return this PXRRecord‘s rdata as a JSON blob

4.4.22. NSAPRecord¶

class dyn.tm.records.NSAPRecord(zone, fqdn, *args, **kwargs)[source]¶

The Network Services Access Point record is the equivalent of an RR for ISO’s Open Systems Interconnect (OSI) system in that it maps a host name to an endpoint address.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an PXRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added nsap – Hex-encoded NSAP identifier ttl – TTL for the record in seconds

nsap¶: Hex-encoded NSAP identifier

rdata()[source]¶: Return this NSAPRecord‘s rdata as a JSON blob

4.4.23. RPRecord¶

class dyn.tm.records.RPRecord(zone, fqdn, *args, **kwargs)[source]¶

The Respnosible Person record allows an email address and some optional human readable text to be associated with a host. Due to privacy and spam considerations, RPRecords are not widely used on public servers but can provide very useful contact data during diagnosis and debugging network problems.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an RPRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added mbox – Email address of the Responsible Person. txtdname – Hostname where a TXT record exists with more information on the responsible person. ttl – TTL for the record in seconds

mbox¶: Email address of the Responsible Person. Data format: Replace @ symbol with a dot ‘.’ in the address

rdata()[source]¶: Return this RPRecord‘s rdata as a JSON blob

txtdname¶: Hostname where a TXT record exists with more information on the responsible person

4.4.24. NSRecord¶

class dyn.tm.records.NSRecord(zone, fqdn, *args, **kwargs)[source]¶

Nameserver Records are used to list all the nameservers that will respond authoritatively for a domain.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an NSRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added nsdname – Hostname of the authoritative Nameserver for the zone service_class – Hostname of the authoritative Nameserver for the zone ttl – TTL for the record in seconds

nsdname¶: Hostname of the authoritative Nameserver for the zone

rdata()[source]¶: Return this NSRecord‘s rdata as a JSON blob

service_class¶: Hostname of the authoritative Nameserver for the zone

4.4.25. SOARecord¶

class dyn.tm.records.SOARecord(zone, fqdn, *args, **kwargs)[source]¶

The Start of Authority Record describes the global properties for the Zone (or domain). Only one SOA Record is allowed under a zone at any given time. NOTE: Dynect users do not have the permissions required to create or delete SOA records on the Dynect System.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an SOARecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added

delete()[source]¶: Users can not POST or DELETE SOA Records

minimum¶: The minimum TTL for this SOARecord

rdata()[source]¶: Return this SOARecord‘s rdata as a JSON blob

rname¶: Domain name which specifies the mailbox of the person responsible for this zone

serial_style¶: The style of the zone’s serial

ttl¶: The TTL for this record

4.4.26. SPFRecord¶

class dyn.tm.records.SPFRecord(zone, fqdn, *args, **kwargs)[source]¶

Sender Policy Framework Records are used to allow a recieving Message Transfer Agent (MTA) to verify that the originating IP of an email from a sender is authorized to send main for the sender’s domain.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an SPFRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added txtdata – Free text containing SPF record information ttl – TTL for the record in seconds

rdata()[source]¶: Return this SPFRecord‘s rdata as a JSON blob

txtdata¶: Free text box containing SPF record information

4.4.27. SRVRecord¶

class dyn.tm.records.SRVRecord(zone, fqdn, *args, **kwargs)[source]¶

The Services Record type allow a service to be associated with a host name. A user or application that wishes to discover where a service is located can interrogate for the relevant SRV that describes the service.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a SRVRecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
port – Indicates the port where the service is running
priority – Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node
target – The domain name of a host where the service is running on the specified port
weight – Secondary prioritizing of records to serve. Records of equal priority should be served based on their weight. Higher values are served more often
ttl – TTL for the record. Set to 0 to use zone default

port¶: Indicates the port where the service is running

priority¶: Numeric value for priority usage. Lower value takes precedence over higher value where two records of the same type exist on the zone/node

rdata()[source]¶: Return this SRVRecord‘s rdata as a JSON blob

target¶: The domain name of a host where the service is running on the specified port

weight¶: Secondary prioritizing of records to serve. Records of equal priority should be served based on their weight. Higher values are served more often

4.4.28. TLSARecord¶

class dyn.tm.records.TLSARecord(zone, fqdn, *args, **kwargs)[source]¶

The TLSA record is used to associate a TLS server certificate or public key with the domain name where the record is found, thus forming a “TLSA certificate association”. Defined in RFC 6698

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create an TLSARecord object

Parameters:

zone – Name of zone where the record will be added
fqdn – Name of node where the record will be added
cert_usage – Specifies the provided association that will be used to match the certificate presented in the TLS handshake. Example values: 0 (CA constraint), 1 (Service certificate constraint), 2 (Trust anchor assertion ), 3 (Domain-issued certificate)
selector – Specifies which part of the TLS certificate presented by the server will be matched against the association data. Example values: 0 (Full certificate), 1 (SubjectPublicKeyInfo)
match_type – Specifies how the certificate association is presented. Example values: 0 (No hash used), 1 (SHA-256), 2 (SHA-512)
certificate – Full certificate or its SubjectPublicKeyInfo, or hash based on the matching type.
ttl – TTL for the record in seconds

cert_usage¶: Specifies the provided association that will be used to match the certificate presented in the TLS handshake

certificate¶: Full certificate or its SubjectPublicKeyInfo, or hash based on the matching type

match_type¶: Specifies how the certificate association is presented.

rdata()[source]¶: Return this TLSARecord‘s rdata as a JSON blob

selector¶: Specifies which part of the TLS certificate presented by the server will be matched against the association data.

4.4.29. TXTRecord¶

class dyn.tm.records.TXTRecord(zone, fqdn, *args, **kwargs)[source]¶

The Text record type provides the ability to associate arbitrary text with a name. For example, it can be used to provide a description of the host, service contacts, or any other required system information.

__init__(zone, fqdn, *args, **kwargs)[source]¶

Create a new TXTRecord object

Parameters:	zone – Name of zone where the record will be added fqdn – Name of node where the record will be added txtdata – Free form text for this `TXTRecord` ttl – TTL for the record. Set to 0 to use zone default

rdata()[source]¶: Return this TXTRecord‘s rdata as a JSON blob

txtdata¶: Free form text