26 karma · joined November 2, 2015
https://zihao.me
zzh8829@gmail.com
[ my public key: https://keybase.io/zihao; my proof: https://keybase.io/zihao/sigs/QdjmAE9RD4vd1N88uuFApDp2yYvn9PJ_V0StbY1FyMc ]
very cool, made it all the way to a checkmate
dig NS @1.1.1.1 test.herokuapp.com -> fail
dig @1.1.1.1 test.herokuapp.com -> fail
dig NS @dns1.p03.nsone.net test.herokuapp.com -> works
dig @dns1.p03.nsone.net test.herokuapp.com -> works
So my conclusion is that NS1 is having issue responding DNS queries from other DNS servers. Interestingly, there is no public information on heroku being dependent on NS1 or any current outages from NS1 status page.For example, API powered by traditional web cserver + database can be replaced with lambda/function + dynamo/s3/firestore. Cron jobs can be replaced by cloud scheduler + lambda/fargate/cloud run. As a serverless user, you really don't interact with "servers", but instead a highly-available and scalable managed task execution environment.
The only downside is each layer of compute abstraction comes at the cost of spending more and more money.