Actually the problem is most likely that the fr24feed program is only resolving the server address at startup. So once it has acquired an ipv6 address it'll hold onto that forever.
What the program should do is periodically re-resolve feed.flightradar24.com and re-connect if the address has changed (or been dropped). That way if they have another catastrophic routing issue they can drop the AAAA address out of the DNS and the clients will eventually all auto-switch over to ipv4.
A restart would have worked as well if flightradar had dropped the AAAA during the problem period, but that doesn't seem to have happened, which is a bit odd. That way at least all those folk attempting a restart would have started working without starting to mess with their systems in an attempt to get them going again.
What the program should do is periodically re-resolve feed.flightradar24.com and re-connect if the address has changed (or been dropped). That way if they have another catastrophic routing issue they can drop the AAAA address out of the DNS and the clients will eventually all auto-switch over to ipv4.
A restart would have worked as well if flightradar had dropped the AAAA during the problem period, but that doesn't seem to have happened, which is a bit odd. That way at least all those folk attempting a restart would have started working without starting to mess with their systems in an attempt to get them going again.
Comment