Embed Notice

@mnot @huitema

there are automation/ease advantages in having your cloud provider be your DNS provider.

it does lock you into their automation and any stupid DNS tricks that aren't RFC standards but do "work" in that environment.

robustness/resiliency does suffer a bit, in that you have both DNS and hosting fail with a provider failure. web browsers and apps will give a different user experience/error if you can resolve the DNS name but be unable to get a working IP connection vs having DNS just SERVFAIL.

i do see more web/app folks that don't really understand DNS at all go for this all-in-one and who don't always understand what tradeoffs they are then living with.