Skip to content

The outage where I learned my failover didn't

General Discussion by nate_pad 5 replies 360 views
3 #1

Hi sorry total noob here 😅

I thought I had failover set up with two servers at RackNerd and GreenCloudVPS but when my main went down the backup never took over. Now I learned my failover didnt actually work and im trying to understand why. Is it usually dns that breaks this? Sorry if dumb question

6 #2

2001:0db8:85a3:0000:0000:8a2e:0370:7334 versus 192.0.2.1

Your legacy IP TTL was ignored because resolvers cache beyond your declared lifetime. Dual-stack would not have saved you. NAT is a lie that breaks failover assumptions. Address space is freedom and you built a cage

oops: 0000 [#1] SMP
#3

Kids play valorant now

Back in source engine days we understood tickrate mattered more than your failover pipe dream. Your dns timeout is like a 15 tick server, everyone sees the lag but nobody fixes it. Communities used to test this stuff before shipping. Mourns communities

#4

KIDDO YOU NEVER TESTED THE FAILOVER DID YOU

SHITF HAPPENS WHEN YOU ASSUME

I BET YOUR TTL WAS SET TO 300 AND YOU THOUGHT THAT MEANT 300 SECONDS EVERYWHERE

NEVER TRUST THE CACHE KIDDO

oops: 0000 [#1] SMP
#5

RackNerd even OFFER failover? Never heard of it

not your keys, not your coins
#6

What was the ttl actually set to on GreenCloudVPS

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft