It definitely is. <ingress>.k8s.<mydns>.com regularly confuses what password I want to use if I have different authentication per ingress. More commonly if I run something else at <name>.<mydns>.com firefox and chrome are both happy to offer up my password for <other service>.<mydns>.com.

Closed. Wont fix.

We solve that problem with the public suffix list. The problem is there's a lot of .name domains, each of which would need to be added to the list.

yes, but other locality domains are fairly static and well-known

.co.uk wouldn't have the same problem because everyone knows that combo is a TLD in and of itself. with a seemingly infinite possible combinations of blah.name that could be a TLD itself, or, might just be a subdomain of .name, it gets really weird