201–210 of 324 posts
Earlier quoted context omitted.
I thought it was funny that they posted information about the outage on the same domain that had the outage.
having a status page on the same domain seems... unfortunate. Other big players have it right, see githubstatus.com
Earlier quoted context omitted.
GoDaddy Registry operates the .us registry. You cannot have a .us domain without their involvement. Consider whether you wanted a .com domain instead (which is operated by Verisign).
zoom.com is an audio equipment manufacturer, which was there before zoom.us. I guess that's what happens where they had to accept substandard domain, because they were unwilling to be creative about their name.
What do relatively large corporations use for their authoritative nameserver? Do they use PowerDNS, knot, bind, or just use the registrar's nameservers?
Google runs their own, Facebook runs their own, Amazon used AWS, Microsoft uses Azure. Netflix uses AWS. Most likely all are running some version of Bind, or something custom.
Earlier quoted context omitted.
They probably meant "whois privacy"[1] (without the space). Whois is basically a way to get information about a domain name (and many other stuff). Whois privacy just ensures that your address, name and other stuff is not public. [1] https://en.wikipedia.org/wiki/Domain_privacy
They were probably joking when they asked that question. Your reply doesn't seem sarcastic, so I take it you genuinely r/whoosh'ed (that's a reference to a subreddit about situations where someone is acting clueless).
Earlier quoted context omitted.
GoDaddy Registry operates the .us registry. You cannot have a .us domain without their involvement. Consider whether you wanted a .com domain instead (which is operated by Verisign).
zoom.com is an audio equipment manufacturer, which was there before zoom.us. I guess that's what happens where they had to accept substandard domain, because they were unwilling to be creative about their name.
Earlier quoted context omitted.
If I were Mauritius, I would be hitting tech companies left and right to secure a permanent income stream. You guys want to kick indigenous people off their land for military bases? Enjoy your new bill for .io domains.
The Chagossians are not by any meaningful standards indigenous. The land was uninhabited when George Washington was rebelling against the British. If the Chagossians are indigenous so are old stock white Americans. And Mauritius have treated the Chagossians like dirt for decades, with no signs of that changing. None of this is to deny the Chagossians were extremely ill treated by the British, but the idea that the Ma…
A lot of Pacific islands territories have complicated histories like this (e.g. Hawaii, New Zealand), but the focus usually ends up on whatever bastards most recently took over from the previous bastards (relative levels of bastardy notwithstanding).
That seriously devalues MarkMonitor's services. MarkMonitor claims to be a "an ICANN-accredited registrar and recognized industry leader since 1999". The whole point of paying for MarkMonitor is that they're an expensive service for valuable domains and are not allowed to screw up. GoDaddy should not be involved here at all.
Imagine being a small startup with a similar problem. Godaddy will not even entertain you.
A few years ago I had a .us TLD. I eventually decided that I probably shouldn't be reliant on a country code for my domain, it's the same reason why I don't use .io I'm not saying that this couldn't have happened with a gTLD But why put your brand at the mercy of a government like that?
What TLD is not subject to a country's laws? .aq? .su? Edit: .eu might be an even better candidate for this requirement, but you can ask British former domain owners how that worked out gTLDs just subject you to an additional layer of incompetence, namely from the company running it. The government where they're located can still come knocking. It's also not like e.g. .nl is run by the Dutch government officials, it'…
ICANN have a mostly hand-off approach to ccTDLs. The intention is that each country decide on their own regulations and management when it comes to their country code specific domains.
.nl is a very special case, and it is true that the Dutch government was not involved. .nl was the first country code TLD created outside of the US, when the domain system still was part of ARPANET and operated by the United States Department of Defense. .nl was then transferred to a foundation 10 years later, and that's where ownership now resides.
ccTLDs are somewhat of a mess. Many are created in universities, then transferred to a company or foundation. Others were sold to companies from the start. In some cases, government have sold their ccTLD to other countries.
.se for example was created in a Swedish university, and then later the government took possession of it (or the university gave it to them, can't really say). Now there are laws that explicitly defines how it should be used and governed, which then a non-profit foundation manage the implementation.
Earlier quoted context omitted.
.us is not a root name server. The root name servers are one more degree removed.
Hence 'for .us'. The trouble with this form of pedantic is that the nicer way to interpret the misunderstanding is that the pedant is ignorant either of language or the structure of dns. "He runs the Internet routers for our company." -> "Your company doesn't run the Internet" -> wtf?
Earlier quoted context omitted.
zoom.com is an audio equipment manufacturer, which was there before zoom.us. I guess that's what happens where they had to accept substandard domain, because they were unwilling to be creative about their name.
Incidentally, Zoom seems a terrible name for a video conferencing app - anyone know why they chose it?