Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Wednesday December 23, 2009 @08:39PM
(#1013210)
And people told me I was crazy for hard-coding IP addresses for s3.amazonaws.com and sdb.amazonaws.com into the Tarsnap code... :-)
[ Parent
| on HN ]
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by akl on Wednesday December 23, 2009 @09:24PM
(#1013265)
You are crazy for doing that - one instance of downtime doesn't justify ignoring all the advantages DNS brings.
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Wednesday December 23, 2009 @09:56PM
(#1013304)
When I made that design decision I wasn't considering the possibility of DNS outages at all; I was just thinking in terms of "there's a huge number of places between me and ultradns where someone could insert a spoofed DNS response".
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by jacquesm on Thursday December 24, 2009 @07:43AM
(#1013743)
What if amazon gets a new netblock assigned ?
Can you forcibly upgrade the software in that case ?
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Thursday December 24, 2009 @11:55AM
(#1014002)
Of course I can upgrade the software; and there's nothing forcible about it. We're talking about code I'm running on my server here...
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by jacquesm on Thursday December 24, 2009 @07:07PM
(#1014566)
Ah, my bad, sorry I thought you meant in the tarsnap client. Then I really don't know why people would make a fuss over you hardcoding the ips in there. All you need to do is keep an eye out in case they change them (which you could even automate).
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Thursday December 24, 2009 @07:42PM
(#1014605)
All you need to do is keep an eye out in case they change them
Exactly, and that's what I do. (With the caveat that I look for AWS endpoints being taken out of service, not for changes in what DNS tells me.)
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by derefr on Wednesday December 23, 2009 @10:04PM
(#1013313)
Are there DNS servers that support versioning? The best solution I could imagine would simply be to set Tarsnap to normally use the current DNS records for S3, but be able to rollback to a valid zone record if they encounter an update that makes the servers stop resolving.
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Wednesday December 23, 2009 @11:35PM
(#1013401)
The Tarsnap client only talks to the Tarsnap server, but I do cache that lookup in order to avoid problems with glitchy DNS resolution.
I could have the Tarsnap server cache DNS lookups if I was only worried about working around DNS outages -- but as I said, that wasn't something I was considering at all when I made the decision to eschew DNS.
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by maw on Thursday December 24, 2009 @10:28AM
(#1013895)
Some DNS caches will continue to try giving out expired records if no newer ones can be found. Unclear that it's worth it, though.
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by baq on Thursday December 24, 2009 @05:13AM
(#1013642)
you can expect such downtimes every Christmas. why? ask yourself how much protection money UltraDNS was told to pay.
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by justinsb on Wednesday December 23, 2009 @08:43PM
(#1013214)
Awesome ... was that for security or for redundancy? Did you have a solution for what would happen if the IP address changed?
Re:Amazon goes down; takes S3, Salesforce, Target, and other...
by cperciva on Wednesday December 23, 2009 @08:57PM
(#1013231)
Mostly security -- DNS is one of the worst offenders when it comes to protocols with security problems, both in terms of protocol issues and bugs in implementations.
Amazon doesn't move endpoints very often, and I round-robin requests to several endpoints; so in the rare cases an AWS endpoint changes I see a slight decrease in Tarsnap performance and can make the Tarsnap server stop using the dead endpoint before any users are likely to notice.