I noticed I alexa integration stopped working some time today. I use DuckDNS and noticed that it’s like it disappeared from the internet. Can’t even access its DNS servers to look up IPs which is why the alexa integration no longer works.
I tried several public dns servers and none can connect to the duckdns dns servers.
Anyone know what’s up?
From time to time an ISP with a automatic malware filter will block the entire DuckDNS domain, because one user site have done something stupid.
Users aren’t using DuckDNS IPs. They are using their own IPs. DuckDNS’s IPs would have nothing to do with it. Also, DuckDNS uses AWS. I have their nameserver IPs and none of them respond. I’ve tested from websites that do ping tests and none of them respond either. There’s something else going on here.
I’ve used afraid.org for many, many years for other things so I’m just going to make the switch to it. It’s rock solid. I was only using duckdns because of it’s easy integration with home-assistant.
The ISP blocks the domain and sometimes even use Deep Packet Inspection for it.
Typically those IPs will be load balancers and they might not be set to respond to ping.
They don’t respond to an nslookup or a ping. I’ve tested from various global nslookup and ping tools. None of the 9 nameservers respond. Poof. Gone from the internet.
I run an IT outsourcing company. We only see something like this when a series of events take down multiple different trunk lines for multiple ISPs feeding a hosting facility or with a major power issue at a facility. Since this is AWS and there are 9 nameservers IPs on several different subnets, I don’t believe any of those scenarios would have occurred.
Outage reports from users in Europe are starting to come in by the dozens this morning.
Chcek one of the downdetectors online then.
I ended up moving to Dynu.
Yeah, posted here showing that they were not serving responses to DNS requests.