| ▲ | __turbobrew__ 2 hours ago | ||||||||||||||||
I don’t believe that there is anything necessarily which requires DNS configs to be global. You can shard your service behind multiple names: my-service-1.example.com my-service-2.example.com my-service-3.example.com … Then you can create smoke tests which hit each phase of the DNS and if you start getting errors you stop the rollout of the service. | |||||||||||||||||
| ▲ | creatonez an hour ago | parent [-] | ||||||||||||||||
Sure, but that doesn't really help for user-facing services where people expect to either type a domain name in their browser or click on a search result, and end up on your website every time. And the access controls of DNS services are often (but not always) not fine-grained enough to actually prevent someone from ignoring the procedure and changing every single subdomain at once. | |||||||||||||||||
| |||||||||||||||||