>> Does the scenario look like this? >> >> * Client asks to registrar to set up frobbit.se > > Yes, someone want to register frobbit.se domain name. For pure > IPR reasons. It should not resolve.
Ah, OK. Then this is first and foremost a registry policy issue: do you in your policy support registration of a place-holder / blocker entries without any associated DNS information or not. The registry in my backyard doesn't support place-holder registrations, insists on delegation-only DNS information, and insists on this being fully operational with a minimum of two name servers before registration can complete. If your naming policy of your registry doesn't formally allow place-holder registrations, insists on delegation-only DNS information, but makes no checks of the supplied information at the time of registration, I agree that this will more or less automatically create lame delegations. That doesn't mean the resulting setup in the DNS is "OK" from a DNS-technical standpoint. However, as a registry or policy body for the registry you're not forced to put yourself in this particular position. (I might have used stronger words...) > Other TLDs are different. That we can agree on :) Regards, - Håvard _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
