2 ms·
One thing to consider is to have your publicly-visible web sites on vanity domain/domains, but all your server infrastructure on a domain in your local stable c
by teddyh 3y ago
One thing to consider is to have your publicly-visible web sites on vanity domain/domains, but all your server infrastructure on a domain in your local stable ccTLD.
- michaelmior 3y agoI recall a HN post within the past few years of an issue with a particular TLD (I think it may have been .io) that resulted in an outage and the conclusion was exactly this. Use whatever nice-looking domain you want for marketing, but stick with something stable for infrastructure.
- yjftsjthsd-h 3y agoWhy does it even matter what domain your servers use internally? Most servers I've ever seen were actually using raw IPs, and the few exceptions used an internal DNS system that couldn't have cared less what the internet thought their domain was.
- organsnyder 3y agoEvolving such an infrastructure is incredibly painful. Want to move to a zero-trust security model? How about migrating only some services to a different provider? Set it up right from the start with a domain name you control (or one that is reserved for private use in an RFC). You can still use internal DNS if you want the additional layer of obscurity.
- teddyh 3y agoPersonally, I prefer to use the internet as it is and not build up and maintain my own parallell infrastructure.
- vidarh 3y agoNot internally, but API endpoints for customers.