Summary

  • EPP domain and host mappings create relationships that can cross client boundaries.
  • A deletion that ignores those relationships can leave dependent domains with too few name servers, require broad updates, or cause resolution failure.
  • RFC 9874 surveys practices such as client-maintained sacrificial hosts, explicit disassociation with restoration and notification, and a special-use sacrificial.invalid approach.

The key event is a delete request against an object that still has associations. RFC 5731 describes domain mappings, while RFC 5732 describes host mappings; RFC 9874 connects their lifecycle implications. A server that allows the deletion may disassociate a host from domains sponsored by other clients. That is an object-lifecycle transition, not DNS cache expiry, domain registration expiry, or BGP route withdrawal.

The protocol authority remains the EPP registry-server relationship and the applicable mappings. RFC 9874 does not define a new EPP command, change who owns registry authority, or require every registry to behave identically. Its recommendations are practices for preserving relational integrity when deletion is destructive. The scope is dependency control across domain and host objects, including cross-client associations, rather than routing policy or contact-mail coherence.

One tempting shortcut is renaming a subordinate host to an external name before deleting it. That can transfer control of the name and expose dependent domains to resolution failure or hijacking if the replacement is registrable or controlled by another party. The risk is not proved merely by the command syntax; it arises from the association graph and from who can control the replacement name.

RFC 9874 reports three preferable patterns: a client can maintain sacrificial name-server hosts; a deletion process can explicitly disassociate, restore, and notify affected parties; or a special-use sacrificial.invalid name can be used. These are recommendations observed in the RFC’s survey, not evidence that all registries implement one of them. Other surveyed practices are not recommended because of undesired side effects.

An EPP Change Poll extension is one available way to inform affected sponsoring clients when registry-side association changes occur. It is a notification mechanism, not a guarantee that clients will react in time. Keeping a domain and its subordinate host associations in pendingDelete can offer a reversible preview during redemption before final purge. That does not make every cross-client transaction reversible at every scale; large association sets may need asynchronous processing.

DNSSEC and multiple authoritative host objects can reduce some risks, but RFC 9874 does not present them as substitutes for dependency-aware deletion. Nor do the RFCs establish adoption, incident frequency, registry performance, or the behavior of any named operator.

Sources