up_the_irons, law: OSPF does equal-cost-multipath routing, where if you are equidistent between two routers originating the same IP block, traffic can use both paths
But there are several problems with that. Firstly, you'd get half the packets in each TCP session going each way, so your two servers need to be the same server and this brings you back to a single point of failure
Also, OSPF is only traditionally used as an IGP inside a single network, not for multiple networks to communicate over an internet
law: For a web service, you could do a lot worse than just announcing multiple A/AAAA records for the website's hostname, possible with some geoip to steer users to the closest ones but that's not vital if your requirements are high-availability rather than high performance
plett, the bad thing about multiple A/AAAA records is that they don't invalidate when the host attached to them goes down
In theory, if you used CNAMEs to point to records that are glued in from a nameserver running on those replicated hosts (or zones), then a lookup for hostA (which points to hostA.zoneA) would fail if hostA.zoneA's nameserver was down. However CNAME+round robin is generally a no-no (not impossible, thanks BIND, but still violates RFC)
Had to interrupt a poudriere build half-way through and couldn't figure out hot to reset all its mounts
reboot system only way. :(
boo
ahh, could have killed the jail apparently
staticsafe: did you hear the new VS voices?
m0unds: i have not
http://www.twitch.tv/planetside2/b/569931098?t=27m08s
male zealot voice or something
"i lack the capacity for pity"
i love that one
haha