101–110 of 229 posts
I am surprised financial institutions don't have any regulation for redundancy. The one that stuck out to me is the Navy Federal Credit Union website being down. I have not had any issues logging into mobile though for some of the reported sites.
Why would Google and Amazon be on the downdetector list or experiencing issues? Don't they have their own DNS / nameservers separate from Akamai?
because the way downdetector works is it just basically counts how many people are searching/visiting for down and if it's much higher than typical it flags the site as down. So if everyone searched "is google down" and visited the link on downdetector that was returned in the search, that would add to the downdetector count for that site. Downdetector doesn't actually know if the site is up or down.
Earlier quoted context omitted.
What's frustrating is that DNS is returning an address, instead of just failing, and so macos is caching that value (though it might be cloudflare doing that).
Wildcard DNS should be a prosecutable crime, punishable by no less than 20 years of hard labor. (Edit: Probably should have made it clear that this was a joke)
You can see this on a lot of sites right now. You get the Akamai style error with something like: Reference: #11.453a2f17.1393u44848484.3aee33433 At the bottom of a very bland looking error page.
Serious question, has anyone properly solved the issue of DNS as a single point of failure?
https://handshake.org is the only project I've seen that actually solves the issue with a decentralized root zone file. https://namebase.io is a "registrar" for it.
https://learn.namebase.io/starting-from-zero/how-to-get-a-na...
This is so convoluted it actually makes the whole thing a non-starter
Many bank systems are disrupted by this in the Netherlands
Serious question, has anyone properly solved the issue of DNS as a single point of failure?
The whole reason it takes a domain 24h to fully work with DNS is because it propagates the information other DNS servers, thus making not be a centralized service.
Serious question, has anyone properly solved the issue of DNS as a single point of failure?
The problem isn't DNS though, is it? The problem is that people don't necessarily use the redundancies on DNS? The whole reason it takes a domain 24h to fully work with DNS is because it propagates the information other DNS servers, thus making not be a centralized service.