5 ms·

Couldn't status.discord.com point to any server?

• 0172 5y ago
  I would also like to know the reason why a subdomain is not sufficient to host a status page as long it's pointing to an independent infrastructure.
  • spc476 5y ago
    subdomain.example.com can be hosted on completely different infrastructure, but what about DNS? Unless you have two different DNS providers for the main domain, you still have single point of failure for the entire domain (and all subdomains).
  • heipei 5y ago
    "Status Update, Monday: Our main domain was suspended / is being blocked for reasons unknown to us. Investigation is ongoing." That happened to notion (notion.so) for example.
• grensley 5y ago
  This assumes it's not a DNS problem, and it's ALWAYS DNS.
  • hinkley 5y ago
    Is that why consul has dns built into it?
    • sascha_sl 5y ago
      The point isn't that DNS is bad, but it is often neglected as a problem source, something taken a bit too much for granted. The Kubernetes community loves this saying because pairing something like nodejs (which doesn't do DNS caching) with a Docker image with no local DNS cache/resolver and a Kubernetes cluster that doesn't usually come with a highly scaled DNS server out of the box often leads to DNS failing more often than anticipated. Also kube-dns, the now deprecated default DNS, was extremely shit. I have a pcap file captured on a kubernetes node with 60000 DNS packets in a 0.2s frame. They're all queries for s3.amazonaws.com.