Earlier quoted context omitted.
I’m there for it; all told it’s not much more than a house …
can't wait to be reachable at come@on.fhqwhgads
This is the kind of stuff you’ll see and know I hit the powerball
171–177 of 177 posts
Earlier quoted context omitted.
Without rigorous ID requirements, that restriction can be circumvented easily.
With rigorous ID requirements, that restriction can be circumvented easily.
.george is a pretty funny one. apparently Walmart owns it, so you probably won't be able to register a .george domain any time soon. https://icannwiki.org/.george do companies even use these in the wild or are they buying these TLDs for nothing? ".brother", ".canon", ".nokia", ".panasonic", ".playstation", ".xbox", ".xerox"... there's even ".sandvikcoromant", which is some sort of Swedish metalwork company.
I wouldn't say it's for nothing. Brands with trademarks have a legal incentive under trademark law to acquire their trademarked name everywhere. Not doing so immediately risks a future legal and bad PR battle if some smaller company acquires it first.
Earlier quoted context omitted.
I wouldn't say it's for nothing. Brands with trademarks have a legal incentive under trademark law to acquire their trademarked name everywhere. Not doing so immediately risks a future legal and bad PR battle if some smaller company acquires it first.
Owning a gTLD isn't the same as registering a trademark. It's on par with petitioning the local government to rename the street your business is on to your business name. There's an incentive to fight for your trademark, Apple would probably sue anyone starting a business with the word Apple in it if there was any chance that the company does anything with technology. However, Apple has no ownership of the word Apple…
To give a slightly ridiculous example (just for fun), just as someone could make pickyourown.apple they could also register tim.apple and start an excellent phishing campaign.
Earlier quoted context omitted.
Run your own DNS then, if you're using your own DNS? Why are your queries for internal systems leaking out to the internet?
I think that the scenario here is where the queries are explicitly not leaking, and you've raised a red herring. If I understand correctly, the scenario is an internal machine named "george", which is being properly search-pathed and looked up as "george.example.org." with nothing leaking anywhere , becoming vulnerable to Walmart being able to issue certificates in the name "george", because the DNS client library's…
HN is full of people from SaaS startups who in essence want to buy the perfect 900 number. But DNS and delegation goes far deeper than selling one name for $20 and going to other $20 names to store your code and email at other SaaS providers.
if you think that answer too short, then read the list of tlds, and then reread the answer. repeat cycle if you need more training for your neural net.
Earlier quoted context omitted.
there was a fight between Apple, the computer company and Apple, the record company (initially owned by The Beatles). They initially resolved it by The Beatles allowing the other to one to keep its name on the condition they would refrain from entering the music business. We all know how that turned out. https://en.wikipedia.org/wiki/Apple_Records
How did it turn out? Seems like both still have their trademark and everyone lived happily ever after