Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DNS Outage at DigitalOcean

status.digitalocean.com

Post reply on HN
Print view View original

121–125 of 125 posts

Re: DNS Outage at DigitalOcean

#121

Post by bitJericho »

scurvy wrote: post #117
bitJericho wrote: post #116

Earlier quoted context omitted.

You can have multiple NS records. You should have ns records that point to different companies DNS servers, and preferably different continents.

That's great for NS records. What about SOA?

Soa isn't used for resolving names afaik.

Re: DNS Outage at DigitalOcean

#123

Post by scurvy »

bitJericho wrote: post #121
scurvy wrote: post #117

Earlier quoted context omitted.

That's great for NS records. What about SOA?

Soa isn't used for resolving names afaik.

You're right. Sorry I meant the NS glue records. Those have a 1 day minimum TTL. If you're not already running multiple providers, switching after one is down won't help much.

Re: DNS Outage at DigitalOcean

#124

Post by scurvy »

scurvy wrote: post #115
sfilipov wrote: post #114

Earlier quoted context omitted.

The answer probably is not very helpful but... change the TTL to a lower value? Is it essential to have such a big TTL of 1 day?

Sure, have fun convincing Verisign. They're the ones controlling the .com registry. Your TTL values are meaningless to them when it comes to SOA. Minimum 1 day TTL.

Sorry, I meant NS glue changes on .com, not SOA.
Post reply on HN