People don't believe me when I say how much DNS matters. So I wrote a song about it. https://soundcloud.com/ryan-flowers-916961339/dns-to-the-tun...
hehe lol
Akamai Edge DNS was down
221–229 of 229 posts
Re: Akamai Edge DNS was down
#222Earlier quoted context omitted.
Last time I tried setting NS to both cloudflare and digital ocean in my domain registry, cloudflare sent me an email saying the configuration is invalid and asked me to revert. Am I doing something wrong?
No, you have done everything right. At least from the point of view of DNS. That you can not use multiple nameservers is a limitation of Cloudflare (limit in the sense of: Cloudflare can only offer their services in the Free and Pro plan if they have full control over all nameservers).
Thank you. I will look into alternative services on the thread then.
Re: Akamai Edge DNS was down
#223Earlier quoted context omitted.
I prefer the browser addon for bitwarden over 1Password. Try editing a site in 1Password. It forces you to log into the full sir, whereas bitwarden can do almost everything right there in the addon.
This is also possible with the 1Password X extension, however there's a lot of feature segmentation and unclear messaging between the Desktop app-based version and 1Password X so I don't blame you for using the old one.
It is? The last I remember, editing a field on 1Password X opens 1Password website instead, where the changes can be made.
Re: Akamai Edge DNS was down
#224So many sites being reported as down, but change your DNS to something else (e.g. Google 8.8.8.8 and 8.8.4.4) and, after flushing your DNS cache, the sites are available. I was unable to get to ups.com or newegg.com (why yes, I am expecting a new toy), but after switching DNS and flushing DNS cache, I was able to get to both. Specifically, 1.1.1.1 provided bad addresses (as opposed to no addresses), and removing 1.1.…
Could you give an example of what you mean by a "bad address" in this context?
Re: Akamai Edge DNS was down
#225Earlier quoted context omitted.
I mean, I guess what I'm saying is that in theory a single provider could purposely keep two different departments that manage their own artifacts independently.
Records have to be kept in sync. If one dept deletes a record and the other doesn’t, how do you decide who’s right? You could add a third dept that gives them both orders, but now that third dept is a single point of failure.
If I were a customer of two different companies for the sake of redundancy, wouldn't I have that same challenge? I could be my own point of failure.
Though, I suppose if I'm responsible for it, I fix it faster for myself.
Re: Akamai Edge DNS was down
#226Earlier 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.
Meh. Without DNS, or something similar, there really is no internet. Obviously you are technically correct.
The internet gets along quite fine without DNS. Packets route from network to network. DNS is an application-layer protocol. People often confuse the web with the internet. We use phone numbers for phone calls. It's conceivable with IPv6 you could nail up your IP address and use a QR code to make the addresses accessible. In a hundred years will DNS still be necessary? I don't think so.
Re: Akamai Edge DNS was down
#227So many sites being reported as down, but change your DNS to something else (e.g. Google 8.8.8.8 and 8.8.4.4) and, after flushing your DNS cache, the sites are available. I was unable to get to ups.com or newegg.com (why yes, I am expecting a new toy), but after switching DNS and flushing DNS cache, I was able to get to both. Specifically, 1.1.1.1 provided bad addresses (as opposed to no addresses), and removing 1.1.…
Could you give an example of what you mean by a "bad address" in this context?
This is from the time of incident:
Server: 1.1.1.1 Address: 1.1.1.1#53
Non-authoritative answer: Name: newegg.com Address: 23.35.185.6
vs
Server: 8.8.8.8 Address: 8.8.8.8#53
Non-authoritative answer: Name: newegg.com Address: 104.80.92.252
104.80.92.252 is newegg.com
23.35.185.6 is a server that provides an error message.
So 1.1.1.1 lied. The proper response would be to reply "I don't recognize that domain". Instead it said, "yeah, I know that, its here..."
Newegg was not down, and when I got macos to forget what it had cached from 1.1.1.1 I was able to use newegg.com fine.
Re: Akamai Edge DNS was down
#228Earlier quoted context omitted.
Records have to be kept in sync. If one dept deletes a record and the other doesn’t, how do you decide who’s right? You could add a third dept that gives them both orders, but now that third dept is a single point of failure.
If I were a customer of two different companies for the sake of redundancy, wouldn't I have that same challenge? I could be my own point of failure. Though, I suppose if I'm responsible for it, I fix it faster for myself.
In this particular case, the Akamai clients did not push broken artifacts, so sounds like at least this particular instance would be avoided.
Re: Akamai Edge DNS was down
#229Earlier 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.…
Ah sorry, you're indeed right. Turns out it was just the .service.gov.uk domain that uses GCP and AWS - I just thought that applied to the parent domain too.
$ dig NS service.gov.uk +short
ns-cloud-e4.googledomains.com.
ns-cloud-e3.googledomains.com.
ns-cloud-e2.googledomains.com.
ns-cloud-e1.googledomains.com.
ns-831.awsdns-39.net.
ns-1983.awsdns-55.co.uk.
ns-117.awsdns-14.com.
ns-1080.awsdns-07.org.