Not only that their support telephone line (in sweden) was down as well
Akamai Edge DNS was down
201–210 of 229 posts
Re: Akamai Edge DNS was down
#202Earlier quoted context omitted.
Depending on what point you draw the line of "single point of failure" you could use multiple providers for your dns. GOV.UK for example uses both aws and gcp for DNS
gov.uk's traffic seems to be handled by Fastly, a well known CDN. What I'm a bit surprised / unsure of is what happens when I run "dig ns gov.uk". The results are: gov.uk. 21559 IN NS ns1.surfnet.nl. gov.uk. 21559 IN NS auth50.ns.de.uu.net. gov.uk. 21559 IN NS ns3.ja.net. gov.uk. 21559 IN NS ns2.ja.net. gov.uk. 21559 IN NS ns0.ja.net. gov.uk. 21559 IN NS auth00.ns.de.uu.net. gov.uk. 21559 IN NS ns4.ja.net. Who is ja.…
whois ja.net
Domain Name: JA.NET
Registry Domain ID: 499794_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.demys.com
Registrar URL: http://www.demys.com
whois uu.net
Domain Name: UU.NET
Registry Domain ID: 5486163_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Re: Akamai Edge DNS was down
#203Earlier quoted context omitted.
gov.uk's traffic seems to be handled by Fastly, a well known CDN. What I'm a bit surprised / unsure of is what happens when I run "dig ns gov.uk". The results are: gov.uk. 21559 IN NS ns1.surfnet.nl. gov.uk. 21559 IN NS auth50.ns.de.uu.net. gov.uk. 21559 IN NS ns3.ja.net. gov.uk. 21559 IN NS ns2.ja.net. gov.uk. 21559 IN NS ns0.ja.net. gov.uk. 21559 IN NS auth00.ns.de.uu.net. gov.uk. 21559 IN NS ns4.ja.net. Who is ja.…
whois ja.net Domain Name: JA.NET Registry Domain ID: 499794_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.demys.com Registrar URL: http://www.demys.com "Demys is a leading provider of corporate domain name management and an ICANN accredited registrar" whois uu.net Domain Name: UU.NET Registry Domain ID: 5486163_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.markmonitor.com surfnet is just an ISP in Netherlands https:/…
Thanks
Is it possible to see if/where is gov.uk using GCP or AWS for its domain zones? From what I can see -- that's not the case? Or am I looking in the wrong place?
Re: Akamai Edge DNS was down
#204Earlier quoted context omitted.
whois ja.net Domain Name: JA.NET Registry Domain ID: 499794_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.demys.com Registrar URL: http://www.demys.com "Demys is a leading provider of corporate domain name management and an ICANN accredited registrar" whois uu.net Domain Name: UU.NET Registry Domain ID: 5486163_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.markmonitor.com surfnet is just an ISP in Netherlands https:/…
Thanks Is it possible to see if/where is gov.uk using GCP or AWS for its domain zones? From what I can see -- that's not the case? Or am I looking in the wrong place?
I think you did the right query, maybe they're using it for different domain names?
Re: Akamai Edge DNS was down
#205Just got booted out of Netflix on the PS4 because the console could no longer connect to Sony's license server. Netflix was working just fine by the way.
Ah thats whats going on. Happened to me as well, I just assumed that Sony is neglecting PS4 performance with its new system, while bogging it down with bloatware.
Re: Akamai Edge DNS was down
#206Earlier quoted context omitted.
It’s just based on user reports, so this is people mischaracterizing it as an AWS outage.
Yep that's my point. I'm guessing that for a lot of sites they can verify if there's an outage pretty easily when they see a spike in reports, but for something like AWS unless they updated their status page (lol) or downdetector ran a bunch of stuff on there just to check with, I guess they don't have a good way to verify it.
Gotcha, yeah I guess I always just considered that out of scope for their service and that it’s just a report aggregator but I suppose you would expect it to be at least a little bit clever based on the “detector” name
Re: Akamai Edge DNS was down
#207Earlier quoted context omitted.
You can still hardcode IP addresses. Not sure most people realize DNS isn't actually needed, you know, except for convenience and all that.
The "Host:" header in http[s] pretty much killed that. Half the internet would be a Cloudflare error page if we moved back to ip addresses :)
Add the name/IP to your local hosts file. It all works great then. Until the server changes IPs, anyways.
I did this with a website I liked which had let the domain expire. It worked for quite some time, until the VPS/whatever expired too. Good thing the Internet Archive is a thing.
Re: Akamai Edge DNS was down
#208Serious question, has anyone properly solved the issue of DNS as a single point of failure?
It’s one of the most successful, global, distributed databases of all time.
What’s the single point of failure?
Re: Akamai Edge DNS was down
#209Serious 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.
More accurately there are distributed caches, which expire on a simple timer basis, as opposed to updates being pushed immediately.
Relatively short TTLs are ubiquitous these days though.
Re: Akamai Edge DNS was down
#210Earlier quoted context omitted.
Why does this need to have the whole NFT / crypto / auction angle? 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
Decentralized control of a centralized finite resource (domain names) requires consensus. For example, Joe Smith and Joe Blow both want joe.com. You want a protocol that gives consistent "global" state without any centralized / trusted users - blockchain/bitcoin is one of the only technical solutions to provide that. I agree that it's a garbage solution in practice, but that's why it's got cryptoshit bundled in. A po…
Agreed. Blockchain is a convoluted solution, but it’s a solution for distributed consensus, if one feels that’s required. But in general I would argue the current root system has served us well and is open and free.
The world you describe, effectively with multiple roots, is coming. Russia have a switch (they’ve even tested it), to anycast out the root DNS IPs within the country, and block them externally. In theory this doesn’t make another “internet” (if IP space is still globally routable,) but in practice it does. Don’t be surprised if other countries follow suit (should they fail to leverage control of current infra via ITU or something.)