4 ms·

Fijivillage.com reports: "All websites and apps hosted in Fiji with the dotcom.fj suffix are currently down and this has also affected Vodafone’s M-PAiSA servic

Fijivillage.com reports: "All websites and apps hosted in Fiji with the dotcom.fj suffix are currently down and this has also affected Vodafone’s M-PAiSA services. This is due to an outage in the University of the South Pacific hosted dotcom.fj domain." [1][2] [1] https://www.fijivillage.com/news/All-websites--apps-in-Fiji-with-dotcomfj-suffix-are-down-and-this-has-also-affected-M-PAiSA-services-x854fr/ https://www.fijivillage.com/news/All-websites--apps-in-Fiji-... [2] https://twitter.com/fijivillage/status/1501070675691278339 https://twitter.com/fijivillage/status/1501070675691278339

londons_explore 5y ago
And this folks is one of the reasons you don't use a 1 minute TTL on your DNS responses...
- Mo3 5y ago
  shamefully opens domain registrar and changes TTL
  - Maxburn 5y ago
    15 min?
    - belorn 5y ago
      I would recommend an hour for almost everything except where very fast updates is expected, in which case 5m is my lowest number (I work at a registrar).
      - slenk 5y ago
        Obviously registrars allow 1m - is there a reason not too besides extra load on DNS servers?
        remram 5y ago
        If the DNS server is out for more than 1 minute you'll get an outage. You also increase latency by preventing anybody from caching the response for more than 1 minute.
        teddyh 5y ago
        There are rumors of DNS resolvers deciding that some TTLs are “too low” to be valid, and applying their own default TTL value instead, thereby negating any benefit a low TTL would have had.
- londons_explore 5y ago
  I use 24 hours on anything I'm not planning on making changes to. High TTL is a better experience for customers because they'll probably have it in local-ish caches even if there is internet routing disruption. And 10 mins on anything I'm about to make changes to. That means if I accidentally make the wrong change, the 'blast radius' is minimized. Obviously, when changing 24h down to 10 mins, keep a close eye on DNS server load, packet loss on links close to it, etc. If in doubt, raise and lower ttl's slowly.

londons_explore 5y ago

And this folks is one of the reasons you don't use a 1 minute TTL on your DNS responses...

Mo3 5y ago
shamefully opens domain registrar and changes TTL
- Maxburn 5y ago
  15 min?
  - belorn 5y ago
    I would recommend an hour for almost everything except where very fast updates is expected, in which case 5m is my lowest number (I work at a registrar).
    - slenk 5y ago
      Obviously registrars allow 1m - is there a reason not too besides extra load on DNS servers?
      - remram 5y ago
        If the DNS server is out for more than 1 minute you'll get an outage. You also increase latency by preventing anybody from caching the response for more than 1 minute.
      - teddyh 5y ago
        There are rumors of DNS resolvers deciding that some TTLs are “too low” to be valid, and applying their own default TTL value instead, thereby negating any benefit a low TTL would have had.
londons_explore 5y ago
I use 24 hours on anything I'm not planning on making changes to. High TTL is a better experience for customers because they'll probably have it in local-ish caches even if there is internet routing disruption. And 10 mins on anything I'm about to make changes to. That means if I accidentally make the wrong change, the 'blast radius' is minimized. Obviously, when changing 24h down to 10 mins, keep a close eye on DNS server load, packet loss on links close to it, etc. If in doubt, raise and lower ttl's slowly.