Why DNSimple Has a Dedicated Status Page Domain | Hacker News Reader

Why DNSimple Has a Dedicated Status Page Domain

blog.statuspage.io

36 pointsstevenklein16 comments

I am sure your customer really appreciates you exploiting their unfortunate outage. This is really what I look for in a company that I depend on when my day is already going terrible.

I have to agree. If I saw this during my downtime, I'd be pretty upset.

I completely agree. This was in bad taste. At least wait for DNSimple to have their service back up.

I second this - I'm a customer of a company that runs on DNSimple; having a status page doesn't help the fact that I can't access my service. There's also @DNSimple for status updates

Unless of course they agreed to it. If not then yes it's a cheap shot.

This is more than ironic: statuspage.io was affected last week by the Amazon DNS outage! That doesn't seem to get a mention.

> Luckily for DNSimple, they were smart enough to run their status page off of their own infrastructure

That wording... is it me, or does that not mean what they think it means?

I read that as "they were smart enough to run their status page on their own infrastructure" because of colloquial uses of the phrase "off of" (eg he jumped off of the dock).

In my own writing, I can usually replace "off of" with "on" 100% of the time.

I see what you mean, but I took it to mean that they ran it "separate from" their own infrastructure, so as it to isolate it from problems affecting their main infrastructure and DNS.

Offtopic but I'm curious - how do you parse "he jumped off of the dock"? To me that would say he was on the dock and jumped off it (into water or whatever), so equivalent to "he jumped off the dock".

I would parse it as "on" in a sentence like "he based his site off of facebook".

I've only ever heard it used as "on" or "from". So I read this as... "run their status page on/from their own infrastructure" too.

Car Salesman: "Sorry to see you've crashed your car...while you're waiting for the ambulance, let me tell you about Volvo...."

> Secondary DNS Provider

You can do that anyway - just delegate the status subdomain as a new zone

> we're unable to add subdomains for existing customers of Fastly

Seems like a bad choice of CDN provider...

> your precious SPF slots

'slots'? You just add another `include` section - there is no number of slots. And even if there was, you don't want email being addressed from a fake looking domain.

The benefits of having a dedicated domain are far and few between. Particularly the reasons listed here are poor ones. It is far more beneficial to use a single trusted domain than to create a confusing mix of domains which look possibly fake.

RFC 4408 Section 10.1 says there is a limit of 10 DNS lookups for SPF entries. SPF validation tools will warn if an entry goes over that limit.

http://www.ietf.org/rfc/rfc4408.txt

Statuspage.io itself is hosted on Route53 exclusively. Guess what will happen when Route53 has a problem...

How about fixing your own shit before pointing fingers at others?

Oh, right. I was wondering what this was and then realised my sites are down. Thanks for telling me, I guess... rather unconventional way. :)

Reply on news.ycombinator.com