News for hackers. Stuff that matters.

A comment on .name Grandfathered. Parent comment

Re:.name Grandfathered by tylergetsay on Tuesday November 10, 2026 @01:33PM (#50444277)
wouldn't that be a problem with a lot of other domains? like locality domains
[ Parent | on HN ]
Re:.name Grandfathered by timeinput on Tuesday November 10, 2026 @01:47PM (#50444456)
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.

[ Parent | on HN ]
Re:.name Grandfathered by mixdup on Tuesday November 10, 2026 @02:36PM (#50445188)
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

[ Parent | on HN ]
Re:.name Grandfathered by OkayPhysicist on Tuesday November 10, 2026 @03:07PM (#50445598)
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.
[ Parent | on HN ]