I'm not sure how toxic it is, but I agree that we are unlikely to have
anything useful to say on the topic.
Speaking personally, I do not see DNAME toxic, but the question has almost
always been:
To clarify, it's us offering advice on what goes into the root zone that's
toxic, not dname specifically.
- How to resolve an interest for having DNAME "work" for the zone apex itself
I think the 2nd of these is a non-issue if "we" do have the assumption
data in TLDs are "delegation only", which I do know is not true for all
TLDs, but it is still what i personally think is the best to do.
The dnames for the Taiwan and Iran TLDs appear to work fine.
There are TLDs with A, AAAA, and MX records (see RFC 7085) but there
aren't many, and if they wanted to use dnames, they could deal with it.
R's,
John
PS: The dnames in .cat don't work at all, but apparently nobody cares.
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
