Hacker News Reader

Comment by john_strinlai | Hacker News Reader

it definitely gets used, and i hope that the application is denied, but i also hope this is another wake up call for people that pick unreserved domains.

View on HN

Wake up to what? The fact ICANN have failed in their governance responsibilities by not encoding a widely used defacto private namespace into the reserved namespace RFC and considering delegating it publicly?

whether you consider this a failure of ICANN or not is completely beside the point.

if you choose to use an unreserved domain, you are choosing to accept the risk of something like this happening. take ownership of your choices. "but other people use it" is not a great defense.

It's a default on OpenWRT and Ubiquiti devices. I don't think consumers should be blamed nor suffer because they didn't know their pricey Ubiquiti router was using a de facto but not officially reserved TLD. you can blame Ubiquiti i guess, but once upon a time there were no reserved TLDs and it was the job of ICANN to deny new ones that had widespread understanding not to be internet routable, so it's not like there's no precedent for Ubiquiti's behavior either.

it would be more defensible of ubiquiti 7 years ago, before the whole .dev situation. not as much anymore

Bear in mind the advice on these things changes over time, and it's possible that the situation in the past may not have been as clear cut.

As an example, at one point in the past (I think in the 90's?), Microsoft recommended using .local for AD domains, whereas now they explicitly recommend against it.

Reply on news.ycombinator.com