111–120 of 283 posts
"“Sunkenness” refers to the fact that intangible assets tend to have little or no market value, unlike, say, land or a factory.
They have value as part of their owner’s business, but not to anybody else.
This means that investment in intangible assets is risky."
https://www.ft.com/content/a01e7262-d35a-11e7-a303-9060cb1e5...
I recommend using easydns.com as the registrar and DNS service. Their email helpdesk is fast: And yeah, you need to have a lot of faith to use .io or other new TLDs which are serviced by new companies.
Okay, anyone want to confirm or add other DNS registrars to the "One of the good ones" list? Ive been recommending my friends to do the entire thing through Dreamhost including a WP install. I personally am more technical, and have my domain name from 7 years ago on godaddy. Any suggestions on where I should use? How about my incompetent friends?
Earlier quoted context omitted.
Would you mind providing some details on this approach? Multiple domains in marketing materials sounds like it would create confusion among customers. Are you specifically referring to companies with an international presence? Thanks
In practice people don't think about or even look at URLs, that's why phishing works. They recognize sites based on logos and stylesheets and often go to places by googling the brand name and clicking on the first link. If you forward every domain to a primary domain at the DNS level, your pagerank probably won't be hurt by this practice.
Forward mycompanyname@gmail.com to info@mycompanyname.com and give it out in the emergency support info for support contracts Add it to your status page as needed, (which should be running on someone else's service or mycompanynamestaus.com).
Customers that really need your service, like the ones who pay, will check the status page and can update the endpoint as needed.
Make sure your sip lines don't point to mycompanyname.com.
If you publish a client side app, use 2 domain names as endpoints, mycompanyname.com and mycompanyname.io. Have the app or service check for and fail over if one doesn't work.
Make sure paging and technician notification is handled by a system that won't be affected by this. (nothing more amazing then getting 200 pages AFTER you've spent 2 days recovering a total failure of a system. You just want to go to sleep but you have to wait for the email queue to drain since you can't turn your pager off.)
Either way, use 2 domain names, and set them to expire at 6 MO intervals. Buy the domain for 2 years (or more) and renew every year so you always have 1-2 year lead time to sort out issues.
The list above would probably cost about $200/year and a few extra hours but it keeps you from getting backed into a corner. Everything else in our infrastructures has fail overs, and limited blast radius for failures.
We tend to us domain registration as a single point of failure and one one even things about it.
i really feel bad for those guys at uptimechecker.io
If you can, just transfer your domains to Google Domains and never worry about shady registrars again. (We also use Dynadot [good], Hexonet [good], Uniregistry [... okay].)
Terrible idea. While Google's registrar seems ok right now, Google's support is nonexistent when things go wrong. Literally every bit of their support is outsourced to 3rd-party companies that provide no path of escalation. Even the really bad registrars (and there are a ton) usually have some direct support (or resell off enom, which will extort your money for the privilege of bailing you out).
If you have a domain registrar with a good support, account the premium you pay as such: a premium for an insurance when things go bad.
That's a horrible situation, and one I'd encourage everyone to try to avoid - register production critical domains with a company that provides live phone support and stick with tried and true TLDs. Yeah, it may cost more, but this story just illustrates that you're staking your entire company on a $15/yr service, and you get what you pay for. Even if you want to run your marketing/landing page/etc off a .io or other…
Used register.com since the 90s. They're so bad I switched 20+ domains to name.com. DO NOT USE web.com or register.com, they're fucking terrible.
And looking at domain.com just now, they don't seem to offer .io domains, so I wonder how he even got the domain there?
That's a horrible situation, and one I'd encourage everyone to try to avoid - register production critical domains with a company that provides live phone support and stick with tried and true TLDs. Yeah, it may cost more, but this story just illustrates that you're staking your entire company on a $15/yr service, and you get what you pay for. Even if you want to run your marketing/landing page/etc off a .io or other…
This is no guarantee. GoDaddy and Google Domains, in particular, have demonstrated willingness to throw you into clientHold hell for political reasons, even for "tried and true TLDs".
I recall a time when a company I had association with lost their main domains due to a failed renewal. In this case it was a long-term employee who left the company that had loads of company bills going to his card. He cancelled the card sometime after he left and the domains were not renewed. I’m not sure where the renewal failure emails were going but probably some unmonitored admin email box. These were very impor…
> A good defense is to limit the renewals for important domains by registering them for as long as possible (10 years) This is an interesting take. I prefer the opposite approach: choose the shortest possible registration window (1 year), and have a very clearly defined, properly-documented renewal process that multiple people at the company understand. It's unlikely that all of those people leave the company in a 1-…
I maintained that having to remember to renew a cert every September was more likely to stick with someone than 18 months or two years. It also keeps your blacklist smaller because dead ones age off faster.
I don’t recall how it ended up but we added automated reminders every 30 days starting three months before expiry.
Do not rely on other people to resolve time-sensitive issues when you can easily avoid it. In this particular case as soon as it's clear the domain hasn't renewed despite being billed then manually renew it using the usual user interface, pay the extra $10 and then contact support after to get one of the charges refunded now the time-sensitivity is gone. The stress alone isn't worth being out of pocket $10 let alone…