On 14 May 2014, at 23:18, Mark Andrews <[email protected]> wrote: > Then why does't the registry remove all the records below a delegation > and any records that refer to them from the published zone when a > delegation is removed?
You're conflating a DNS zone (published from a database) from the registry (which is the database). You need to think in terms of (a) the data model and associated constraints in the database, which relates (perhaps indirectly, via a registrar) with the instructions received from a registrant, and (b) the scheme by which a zone is produced. For example, in (some? all?) gTLD registries there's a constraint on removing a domain object that has subordinate host object dependencies, and there's a constraint on removing host objects that have non-superordinate domain object dependencies. The way people work around this in practice is with hacks, as was seen at the top of this thread. Once the data constraints are worked around, you publish a zone. Joe _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
