4 ms·

We feel the pain as well as our platform is unreachable. I'm now using an other DNS server and changed the nameserver in the domain-record. However the DNS prop

We feel the pain as well as our platform is unreachable. I'm now using an other DNS server and changed the nameserver in the domain-record. However the DNS propagation is taking some time. What are you doing at the moment as fail-over?

pbhjpbhj 11y ago
Sorry if I'm trying to "teach grandma to suck eggs" but can't you just enter the domain in your local hosts file. If it's a network that needs access then presumably you have some sort of proxy/cache that could be seeded with the necessary domain+IP pairing? I suppose these aren't possible if you're trying to demo on someone else's network or in a public space or such.
traviswingo 11y ago
We just switched it over to Route53 and set up some fail-overs there. Took us 5 mins and we're back online. Looks like DO is still offline so it seems to have been a good call...
- scurvy 11y ago
  You're back online from your perspective. What about all the name servers that have your SOA cached still looking at DO? You're still down for them.
  - traviswingo 11y ago
    Tough shit, lol. We now have reduced TTL times for future occurrences, but there's nothing we can do for those users who are still experiencing an outage.
    - scurvy 11y ago
      Minimum TTL for SOA records on .com is a day. Lowering your A record TTL isn't buying you much in case of DNS hosting failure. Helpful if your site (not dns) needs to move providers though.