3 ms·
But this is only a procedure for the customer. We'd hope that their employees have internal rules that are just as strict for interacting with internal IT, but
by viraptor 6y ago
But this is only a procedure for the customer. We'd hope that their employees have internal rules that are just as strict for interacting with internal IT, but can't be sure.
The rules for the customer don't matter much is it get hold of a company account which can make the right change.
Re. Cryptocurrency, I'd be really nervous implementing that in production. The current registers may not be perfect, but there's an escape hatch where things go wrong, you contact the right people and changes get reverted. With coin based DNS, the right hack may mean you lose access to your domain forever and there's no rollback possible.
- CydeWeys 6y agoYup. If you're running something this critically important on your domain (i.e. pretty much any business doing 7 figure revenue or more), it'd really behoove you to switch to a registrar that supports registry lock on your domain. Then you're protected by the procedures at two unrelated business entities.