kvz

31 ms·

301.
by kvz 14y ago
We notice the outages because customers tell us to upload x to y.com. If that fails because of 'unable to resolve y.com', we get a support ticket. I guess for your average web 2.0 the effects are less harsh. Also as Amazon said, these outag
302.
by kvz 14y ago
A timeout of 1 can result in false positives. 3 seconds is recommended according to the manpage. Should the occasional false positive be none of your concern, then you still add at least a second to every request. If you make many, that's m
303.
by kvz 14y ago
From the manpage: "[rotate] causes round robin selection of nameservers from among those listed". This means in your configuration, the broken nameserver will be hit once every 3 times, resulting in a 1second timeout before trying the other
304.
by kvz 14y ago
Using IPs for communication to Amazon RDS instances is inadvisable. You'd have to use WAN addresses outside of EC2, and LAN addresses inside of EC2. Addressing them by domain resolves this. Additionally I don't think Amazon guarantees your
305.
by kvz 14y ago
Thanks for the link! I did find dnrd ( http://dnrd.sourceforge.net/ ), but I really wasn't looking into proxying DNS requests and introducing another daemon / dependency, that could at some point fail or get confused, requiring even more te
306.
Let's Make DNS Outage Suck Less(kvz.io)
37 points by kvz 14y ago|14 comments
307.
Run Node.js as a Service on Ubuntu(kvz.io)
1 points by kvz 14y ago|0 comments
308.
Vagrant Tip: Sync VirtualBox Guest Additions(kvz.io)
1 points by kvz 14y ago|0 comments
309.
Quick server debugging with WTF(kvz.io)
1 points by kvz 14y ago|0 comments
310.
by kvz 14y ago
I assumed a year had 52 weeks. 2009 had 53.