octodns.record.caa
Classes
|
|
|
|
|
Checks that CAA records include an explicit |
|
Strict CAA rdata validator per RFC 8659 §4.1. |
|
Validates CAA rdata: |
- class octodns.record.caa.CaaValueValidator(id, sets=None)[source]
Bases:
ValueValidatorValidates CAA rdata:
flagsis an integer in [0, 255], andtagandvalueare present.- validate(value_cls, data, _type)[source]
Validate a record’s rdata values.
- Parameters:
value_cls (type) – The concrete value class being validated (e.g.
MxValue,_Ipv4Value). Validators that need access to value class-level attributes (e.g.VALID_ALGORITHMS,_address_type) should read them fromvalue_cls. Per-instance configuration should live onself, not onvalue_cls.data (list | tuple | str | dict) – The rdata to validate. For multi-value record types this is a list/tuple of value dicts or strings; for single-value types it may be a bare value. Most validators iterate
datadirectly — when a validator needs to accept either form it should normalize withif not isinstance(data, (list, tuple)): data = (data,)._type (str) – The record type string (e.g.
'MX','A'). Passed through to helpers like_check_target_formatwhich format it into their reason strings.
- Returns:
A list of human-readable reason strings describing validation failures. Must return an empty list when the values are valid. Reasons from multiple validators are concatenated by the caller, so each reason must stand alone without context from the others.
- Return type:
Notes
Implementations must not raise on invalid input — all failures are reported via the returned list. Reason strings are surfaced verbatim in
ValidationErrormessages, so phrasing and punctuation should be stable across releases.
- class octodns.record.caa.CaaValueRfcValidator(id, sets=None)[source]
Bases:
ValueValidatorStrict CAA rdata validator per RFC 8659 §4.1.
flagsmust be 0 or 128 — only bit 0 (Issuer Critical) is defined; all other bits are reserved and must be zero.tagmust match[a-zA-Z0-9]+.
Enabled as part of the
strictvalidator set:manager: enabled: - strict
- _tag_re = re.compile('^[a-zA-Z0-9]+$')
- validate(value_cls, data, _type)[source]
Validate a record’s rdata values.
- Parameters:
value_cls (type) – The concrete value class being validated (e.g.
MxValue,_Ipv4Value). Validators that need access to value class-level attributes (e.g.VALID_ALGORITHMS,_address_type) should read them fromvalue_cls. Per-instance configuration should live onself, not onvalue_cls.data (list | tuple | str | dict) – The rdata to validate. For multi-value record types this is a list/tuple of value dicts or strings; for single-value types it may be a bare value. Most validators iterate
datadirectly — when a validator needs to accept either form it should normalize withif not isinstance(data, (list, tuple)): data = (data,)._type (str) – The record type string (e.g.
'MX','A'). Passed through to helpers like_check_target_formatwhich format it into their reason strings.
- Returns:
A list of human-readable reason strings describing validation failures. Must return an empty list when the values are valid. Reasons from multiple validators are concatenated by the caller, so each reason must stand alone without context from the others.
- Return type:
Notes
Implementations must not raise on invalid input — all failures are reported via the returned list. Reason strings are surfaced verbatim in
ValidationErrormessages, so phrasing and punctuation should be stable across releases.
- class octodns.record.caa.CaaValueBestPracticeValidator(id, sets=None)[source]
Bases:
ValueValidatorChecks that CAA records include an explicit
issuewildproperty whenever anissueproperty is present.Per RFC 8659 §4.2, wildcard certificate issuance falls back to
issuepolicy when noissuewildrecord exists; omittingissuewildmakes the wildcard-issuance policy implicit rather than explicit.Enabled as part of the
best-practicevalidator set:manager: enabled: - best-practice
- validate(value_cls, data, _type)[source]
Validate a record’s rdata values.
- Parameters:
value_cls (type) – The concrete value class being validated (e.g.
MxValue,_Ipv4Value). Validators that need access to value class-level attributes (e.g.VALID_ALGORITHMS,_address_type) should read them fromvalue_cls. Per-instance configuration should live onself, not onvalue_cls.data (list | tuple | str | dict) – The rdata to validate. For multi-value record types this is a list/tuple of value dicts or strings; for single-value types it may be a bare value. Most validators iterate
datadirectly — when a validator needs to accept either form it should normalize withif not isinstance(data, (list, tuple)): data = (data,)._type (str) – The record type string (e.g.
'MX','A'). Passed through to helpers like_check_target_formatwhich format it into their reason strings.
- Returns:
A list of human-readable reason strings describing validation failures. Must return an empty list when the values are valid. Reasons from multiple validators are concatenated by the caller, so each reason must stand alone without context from the others.
- Return type:
Notes
Implementations must not raise on invalid input — all failures are reported via the returned list. Reason strings are surfaced verbatim in
ValidationErrormessages, so phrasing and punctuation should be stable across releases.
- class octodns.record.caa.CaaValue(value)[source]
Bases:
EqualityTupleMixin,dict- VALIDATORS = [<octodns.record.caa.CaaValueValidator object>, <octodns.record.caa.CaaValueRfcValidator object>, <octodns.record.caa.CaaValueBestPracticeValidator object>]
- property flags
- property tag
- property value
- property data
- property rdata_text