wouldn't that be a problem with a lot of other domains? like locality domains

timeinput 4 hours ago | parent | next [-]

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.

▲

OkayPhysicist 3 hours ago | parent | prev | next [-]

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.

▲

mixdup 3 hours ago | parent | prev [-]

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

	▲	toast0 an hour ago \| parent [-]
		> with a seemingly infinite possible combinations Verisign claimed approximately 22,000 third level domains [1] in July 2026. I don't see an estimate of the number of shared second level domains, but it's finite. The current public suffix list includes 10414 names [2]; so at maximum, the list would approximately triple in size --- not ideal, but feasible. [1] https://itp.cdn.icann.org/en/files/consensus-policies/fessen... [2] including some with wildcards, re: your other post