3 ms·
Sure, but there are advantages to have them available on the internet as well. What I’m thinking is having a seperate domain, which many companies already have
by mrweasel 6y ago
Sure, but there are advantages to have them available on the internet as well.
What I’m thinking is having a seperate domain, which many companies already have, for corporate services. We have a .dk for our actual service, products and email, but we also use a .net domain for things like AD, Azure integration and a ton of auxilary services.
Having .company rather than .company.net is just a “nice to have” and certainly not worth the $185,000 registration fee. Had it been cheaper I could see many chooce to have their own TLD just to have a more clear border between “infrastructure” and “product”. It gives the IT department more control of the domains they wish to allocate without stealing the from the product and marketing teams. I worked for a company where we already used a series of subdomains, for backend stuff, but down the road those same subdomains became more and more relevant to free up for the public parts of our website, and it was a pain to move around.