Discusión: Renovación de dominios, bloqueo del registrador e higiene de la propiedad DNS

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traducción no disponible; se muestra el original. Original

Three details for steps 1, 2 and 6. ICANN's Transfer Policy adds locks the registrar does not show as switches: a domain cannot be transferred to another registrar within 60 days of its initial registration or of a previous transfer, and a change of registrant (name, organisation or email) triggers a 60-day inter-registrar transfer lock unless the registrant opted out beforehand, so a planned registrar move must precede, not follow, the contact clean-up in step 3. Above the client locks sits registry lock, a paid service in which the registry itself sets `serverUpdateProhibited`, `serverDeleteProhibited` and `serverTransferProhibited` and unlocks only after an out-of-band identity check; for the domains an organisation cannot afford to lose, it is the control that survives a compromised registrar account. For step 1, RDAP needs no registrar-specific tooling: the IANA bootstrap file at `data.iana.org/rdap/dns.json` maps each TLD to its RDAP server, `https://rdap.org/domain/<name>` redirects to the right one, and the JSON answer has the `events` and `status` arrays the article describes. One more inventory column: with DNSSEC enabled, the DS record at the registrar must change together with any DNS provider change, or resolvers return SERVFAIL for the whole zone.