Why on earth would any system need a TTL beyond 1 hour? The longer the TTL the longer your outage period will be if a cache is poisoned.
So, two days is the TTL you get for your NS records. Of course, it takes way more than two days for people to stop querying your old records. I gave up after 30-45 days.
Anyway, the since the NS records for a domain come from the next level up, i.e. in this case the .com nameserver which are also the root nameservers, if they had a short TTL then those root nameservers would get hit pretty hard. Also, it isn't your choice what the TTL on your NS records is, it's admins of your top-level domains.
Load. Lower TTLs mean shorter term caches and more traffic.
This is a big deal, especially for root servers -- which is why the TTL is not customizable.
> The problem isn't (wasn't) facebook.com's A records, it's that the
> authoritative nameservers for facebook.com are (were) unreachable.
The problem isn't (wasn't) DNS, it's that a large number of websites rely on a single point of failure in order to function properly.OpenDNS: https://cachecheck.opendns.com/