Can all registered uses please login, even just for a few minutes..
It helps build a picture where our "good traffic" is coming from..
Thanks :)
It helps build a picture where our "good traffic" is coming from..
Thanks :)
Server updates
Re: Server updates
Server will be having some DNS updates and fixes now. Some people may see DNS errors until its all tried and tested.
Re: Server updates
IPv6 was down for three days, and here is why
If you connect over IPv6, the site has been unreachable since Tuesday morning. Everything on IPv4 carried on as normal, which is exactly why it went unnoticed for so long.
The cause turned out to be a routine package upgrade on the 11th. systemd-networkd restarted as part of it, the server lost its global IPv6 address, and it never got it back. The interface stayed up throughout, so nothing looked broken from the inside.
A packet capture showed what was really going on. The server was asking the network for its address, the network was answering correctly within a couple of milliseconds every single time, and the server was then quietly losing its nerve and asking again. Two minutes later, same question, same answer, same silence. It kept this up for three days without ever once completing the conversation.
The fix was to stop asking. The address is derived from the network card and never changes, so it is now set statically instead of being requested at boot. That removes the broken exchange from the picture entirely.
One unexpected bonus: a couple of days of intermittent email delays turned out to be the same fault, and those have gone too.
If you connect over IPv6, the site has been unreachable since Tuesday morning. Everything on IPv4 carried on as normal, which is exactly why it went unnoticed for so long.
The cause turned out to be a routine package upgrade on the 11th. systemd-networkd restarted as part of it, the server lost its global IPv6 address, and it never got it back. The interface stayed up throughout, so nothing looked broken from the inside.
A packet capture showed what was really going on. The server was asking the network for its address, the network was answering correctly within a couple of milliseconds every single time, and the server was then quietly losing its nerve and asking again. Two minutes later, same question, same answer, same silence. It kept this up for three days without ever once completing the conversation.
The fix was to stop asking. The address is derived from the network card and never changes, so it is now set statically instead of being requested at boot. That removes the broken exchange from the picture entirely.
One unexpected bonus: a couple of days of intermittent email delays turned out to be the same fault, and those have gone too.