2.1. Domains

The life cycle of a domain is influenced by registration expiration, validation expiration (in ENUM domains), and eventually by forced presence in a zone (in or out) and prohibitions.

2.1.1. Registration expiration

This section describes a flow of states related to domain registration expiration.

Setting:

automatically

Visible:

internally or externally

Allowed for:

domains

Affects:

zone presence, existence

Domain registration expiration

Legend

Basic flow

• 0 (zero state)
  When a domain is freshly registered or renewed, none of the flags is on.

• expW (internal)
  When the expiration date is approaching, by default 30 days before expiration (configurable by the expiration_notify_period parameter), the expirationWarning flag is set, which may trigger a notification.

• expired
  When the actual expiration date arrives, the expired flag is set, which may trigger a notification.
  However, the domain is still generated to the zone for some time.

• ouW (internal)
  25 days after expiration (configurable by the outzone_unguarded_email_warning_period parameter), the outzoneUnguardedWarning flag is set, which may trigger a notification.

• unguarded
  30 days after expiration (configurable by the expiration_dns_protection_period), the domain becomes unguarded (and is flagged so), which results in exclusion from the zone (flagged also outzoneUnguarded).

• delW (internal)
  34 days after expiration (configurable by the expiration_letter_warning_period parameter), the deletionWarning flag is set, which may trigger a notification.

• deleteCandidate
  61 days after expiration (configurable by the expiration_registration_protection_period parameter), the deleteCandidate flag is set, unless there is delete prohibition on the domain. If set, the domain cannot be renewed anymore and the Registry is allowed to delete the domain.

The flags accumulate. (Each state includes flags of the preceding state, e.g. when a domain has the expired flag, it also has the expirationWarning flag.)

The flags are unset when the domain is renewed.

Prohibitions

Setting of the renew prohibition will cause the domain to be taken out of the basic flow (none of those flags will be set). The expiration flags are, however, returned to the domain (re-calculated according to the current date), once the renew prohibition has been revoked.

Delete prohibition prevents the Registry from setting the deleteCandidate flag on the domain and consequently deleting the domain, until the delete prohibition is revoked.

Zone-inclusion according to registration states

State	0	expW	expired	ouW	unguarded	delW	delCandidate
Allows inclusion	Yes	Yes	Yes	Yes	No	No	No

Formal rules

See Domain registration expiration rules.

2.1.2. Validation expiration

This section describes a flow of states related to ENUM domain validation expiration.

Setting:

automatically

Visible:

internally or externally

Allowed for:

ENUM domains

Affects:

zone presence

ENUM domain validation expiration

Legend

Basic flow

• 0 (zero state)
  When a domain is freshly registered or its validation expiration date renewed/updated, none of the flags is on.

• valW1 (internal)
  When the validation expiration date is approaching, 30 days (configurable) before validation expiration, validationWarning1 flag is set, which may trigger the 1st warning notification.

• valW2 (internal)
  When the validation expiration date is approaching, 15 days (configurable) before validation expiration, validationWarning2 flag is set, which may trigger the 2nd warning notification.

• notValidated
  When the actual validation expiration date comes, notValidated flag is set, which results in the domain not being generated to the zone anymore.

The flags accumulate. (Each state includes flags of the preceding state, e.g. when a domain has the notValidated flag, it also has the validationWarning1 and validationWarning2 flags.)

The flags are unset when the validation is renewed/updated.

Prohibitions

Prohibitions do not affect this flow.

Zone-inclusion according to validation states

State	0	valW1	valW2	notVal
Allows inclusion	Yes	Yes	Yes	No

Formal rules

See ENUM domain validation rules.

2.1.3. Zone presence

There are two ways to determine whether a domain shall be generated to a zone.

The domain is naturally included in the zone if and only if it meets the following conditions:

• the domain is not unguarded, and

• the domain is validated if it is an ENUM domain, and

• the domain has an nsset assigned to it, and

• the domain is not forced out of the zone manually, i.e. it does not have the serverOutzoneManual flag.
  This flag forces the domain not to be included despite having met the conditions above.

The domain can be forced to the zone by setting the manual flag serverInzoneManual. This can override registration expiration flow up to deleteCandidate and expired validation. However, if the domain does not have an nsset, this flag will not have the desired effect.

Neither of these manual flags affects the basic flow.

When the domain is not generated to the zone for any reason, it is indicated with the outzone flag.