9. Communication

This chapter provides an overview of communication which is triggered by events in the Registry.

9.1. Channels

The FRED is capable of using the following channels of communication:

  • Email
    • mandatory in contacts and registrars
    • used for most communication
  • Notify email
    • optional, contacts only
    • used for notifications only
    • If a contact does not have a notify email, it is not notified.
  • Generic and additional emails
  • Poll messages
    • an integral part of EPP
    • used for communication with registrars related to EPP activity
  • Letter CZ-specific
  • Registered letter CZ-specific
  • SMS CZ-specific

9.1.1. Generic email addresses CZ-specific

The generic email addresses are a qualified guess in an attempt to reach domain stakeholders. The Registry applies a set of patterns with local-part names which the stakeholders often use to name their domain-based mailboxes.

The generic email addresses are generated based on the following patterns: info@<fqdn>, kontakt@<fqdn>, postmaster@<fqdn>, <fqdn>@<fqdn> where <fqdn> is the domain name in question.

The patterns for the generic email addresses are hard-coded.

9.2. Object modifications

This section describes communication that arises from modifications of registrable objects by registrars, except the system registrar.

Modifications must finish successfully for notifications to occur.

Name Trigger Addressee Channel
Create notification     Notify email
(CS params)
  Registrar created a domain Holder and admin. contacts  
  Registrar created a contact The contact  
  Registrar created an nsset Tech. contacts  
  Registrar created a keyset Tech. contacts  
       
Delete notification     Notify email
(CS params)
  Registrar deleted a domain Holder and admin. contacts  
  Registrar deleted a contact The contact  
  Registrar deleted an nsset Tech. contacts  
  Registrar deleted a keyset Tech. contacts  
       
Renew notification Registrar renewed a domain Holder and admin. contacts Notify email
(CS params)
       
Transfer notification     Notify email
(CS params)
  Registrar transferred a domain Holder and admin. contacts  
  Registrar transferred a contact The contact  
  Registrar transferred an nsset Tech. contacts  
  Registrar transferred a keyset Tech. contacts  
  Registrar transferred an object Previous registrar Poll message (structure)
       
Update notification     Notify email
(CS params)
  Registrar updated a domain Holder and admin. contacts
both old and new
 
  Registrar updated a contact The contact
both old and new notify email
 
  Registrar updated an nsset Tech. contacts
both old and new
 
  Registrar updated a keyset Tech. contacts
both old and new
 

9.2.1. Settings

Configuration allows to disable all EPP notifications in the Registry altogether (allowed by default):

Configure in the fred-rifd configuration file
[registry]
disable_epp_notifier = true

It is also possible to allow registrars to disable EPP notifications per command by configuring a special prefix for client transaction identifiers:

Configure in the fred-rifd configuration file
[registry]
disable_epp_notifier_cltrid_prefix = no_notification_

When the registrar signs a command with a client transaction identifier starting with the prefix no_notification_, the operation will not trigger a notification.

9.3. Life-cycle events

This section describes communication that arises from the life cycle of registrable objects (state changes).

Name Trigger Addressee Channel
Expiration warning Domain expiration is approaching – the expW state has been reached Registrar Poll message (structure)
Expiration notice Domain has expired Holder and admin. contacts Email (CS params)
    Registrar Poll message (structure)
Outzone warning (unguarded) Domain is becoming unguarded – the ouW state has been reached Generics + additionals Email (CS params)
Outzone notice (unguarded) Domain has become unguarded Holder and admin. contacts Email (CS params)
    Technical contacts of the domain’s nsset Email (CS params)
    Registrar Poll message (structure)
Deletion warning
CZ-specific
Domain is going to be deleted – the delW state has been reached Holder Letter
Deletion notice Domain is being deleted – the deleteCandidate state has been reached Holder and admin. contacts Email (CS params)
    Technical contacts of the domain’s nsset Email (CS params)
    Registrar Poll message (structure)
1st validation warning Validation of an ENUM domain is expiring – the valW1 state has been reached Registrar Poll message (structure)
2nd validation warning Validation of an ENUM domain is expiring – the valW2 state has been reached Holder and admin. contacts of the domain Email (CS params)
Outzone notice (not validated) Validation of an ENUM domain has expired – the domain is not validated anymore Holder, admin. contacts and tech. contacts of the nsset Email (CS params)
    Registrar Poll message (structure)
Unused notification Object (nsset, keyset, or contact) has become obsolete and is being deleted Technical contacts or the contact Notify email (CS params)

9.3.1. Outzone unguarded warnings

These warnings are sent to generic and additional custom email addresses which are not direcly related to records in the Registry database.

Additional email addresses can be manually loaded to the Registry in the WebAdmin (Daphne). You just import a CSV file with domain names and lists of email addresses to send the warning email to.

Example of a line in a CSV file with additional emails
domain.tld,mail@example.tld,anothermail@example.tld,etc@example.tld

After the warnings are sent, the list of additional email addresses is cleared in the Registry database. A new list of addresses must be imported if there is need for another warning of this type.

9.3.2. Settings

To disable these messages, remove the corresponding row in the database table notify_statechange_map for the state change you do not wish to communicate.

To modify when the messages are sent, reconfigure parameters of the life cycle itself.

9.4. Administrative events

This section describes communication that arises from administrative tasks of the Registry.

Name Trigger Addressee Channel
Contact merger Registry has merged a contact automatically because it was detected as a duplicate The contact Email (CS params)
Object update (contact merger) Registry has updated an object as a result of contact merger (replaced duplicate contacts in linked objects) Registrar Poll message (structure)
Contact update (address disclosure) Registry has changed disclosure of contact address (contact has started or stopped complying with the rules for hiding address) Registrar Poll message (structure)
Contact reminder Contact registration anniversary is approaching in 2 months The contact Email (CS params)
Domain update (Admin.blocking) Registry has updated a domain Registrar Poll message (structure)
Domain delete (Admin.verification) Registry has deleted a domain Registrar Poll message
Tech.check results Registry has carried out a check requested by a registrar Registrar Poll message (structure)
Tech.check results Registry has carried out a periodic check, which has failed Technical contacts of the nsset Email (CS params)
Automatic keyset management – Acceptance period iniated Registry has discovered valid CDNSKEY records on an insecured domain Technical contacts of the nsset Email
Automatic keyset management – Acceptance period broken Registry has detected that CDNSKEY records changed during the acceptance period Technical contacts of the nsset Email
Automatic keyset management – Acceptance period completed Registry has updated a domain with the newly accepted key set See Update notification  
    Registrar Poll message (structure)
Automatic keyset management – Keys update Registry has discovered new valid CDNSKEY records on a secured domain Technical contacts of the nsset Email (CS params)

9.5. Public request events

This section describes communication that arises from requests of the public submitted through a web form.

Name Trigger Addressee Channel
Authinfo Request for authinfo, which has been placed as a public request Linked contacts or the contact Email (CS params)
Authinfo Request for authinfo, which has been placed through a registrar Linked contacts or the contact Email (CS params)
Blocking confirmation Public request for object (un)blocking has been executed Linked contacts or the contact Email (CS params)
Personal information Request for personal information, which has been placed as a public request The contact Email (CS params)

9.6. Registrar events

This section describes communication that arises from registrar administration.

Name Trigger Addressee Channel
Low credit Registrar’s credit has dropped below the limit Registrar Poll message (structure)
Request usage Daily (depends on the task setup) Registrar Poll message (structure)
Monthly bill – No audit invoice
CZ-specific
The end of the month in which paid services were not used Registrar Email
Monthly bill – Audit invoice included
CZ-specific
The end of the month in which paid services were used Registrar Email
Confirmation of a received payment for credit deposit – Advance invoice included
CZ-specific
An advance payment has been matched Registrar Email

9.6.1. Settings

The credit limit for the low credit message can be configured per zone in the database table poll_credit_zone_limit.