Skip to content

Forbid subordinate host changes when superord domain is locked#3171

Open
gbrodman wants to merge 1 commit into
google:masterfrom
gbrodman:blockLockedHostUpdates
Open

Forbid subordinate host changes when superord domain is locked#3171
gbrodman wants to merge 1 commit into
google:masterfrom
gbrodman:blockLockedHostUpdates

Conversation

@gbrodman

@gbrodman gbrodman commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

This is not explicitly called out that I could find in the RFCs, however it is very clear from the RFCs that hosts are subordinate to their domains and it stands to reason that updates to a subordinate host are updates to the superordinate domain.

Section 1.1 of RFC 5732 specifies:

host name "ns1.example.com" has a subordinate relationship to domain
name "example.com". EPP actions (such as object transfers) that do not
preserve this relationship MUST be explicitly disallowed.

Allowing host updates (e.g. renames) opens up situations where this relationship could be severed. We add analogous prohibitions on deletion and creation of subordinate hosts as well.

b/534930957


This change is Reviewable

This is not explicitly called out that I could find in the RFCs, however
it is very clear from the RFCs that hosts are subordinate to their
domains and it stands to reason that updates to a subordinate host are
updates to the superordinate domain.

Section 1.1 of RFC 5732 specifies:

```
host name "ns1.example.com" has a subordinate relationship to domain
name "example.com". EPP actions (such as object transfers) that do not
preserve this relationship MUST be explicitly disallowed.
```

Allowing host updates (e.g. renames) opens up situations where this
relationship could be severed. We add analogous prohibitions on deletion
and creation of subordinate hosts as well.

b/534930957
@gbrodman

Copy link
Copy Markdown
Collaborator Author

note: this PR explicitly does not forbid host updates where the superordinate domain has CLIENT_UPDATE_PROHIBITED set. This is for two reasons.

  1. registrars can just remove that status anyway
  2. there are 1688 current superordinate domains with CLIENT_UPDATE_PROHIBITED set, and only 1 with SERVER_UPDATE_PROHIBITED set and I'm wary of changes that affect so many domains

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant