Amazon Echo devices stop working - no Connection possible

[Onslaught]

Since last Night, the Amazon Echo devices can‘t Connect to the Amazon Servers, if AdGuard is set as DNS Service (normal DNS Servers and DNS over TLS).

when another DNS Service is configured (DNSForge.de), the Amazon devices can reconnect and work.
Was there a Filter Update last night that forces the Amazon devices to stop connecting?

 

[Julien]

hello, I am in the same situation. No more amazon access with Alexa. An idea ? Thank you.

 

[Blaz]

Without such device not possible to test

If a user has AdGuard Home and such device, then it would be easier to fix.

Edit: Looks like this issue:

Filter ||a2z.com^ breaks Alexa-Devices · Issue #808 · AdguardTeam/AdGuardSDNSFilter

The ||a2z.com^ filter (via easy privacy) causes Alexa devices to stop working. avs-alexa-14-eu.amazon.com blocked by CNAME:

github.com

 

[Onslaught]

Without such device not possible to test

If a user has AdGuard Home and such device, then it would be easier to fix.

Edit: Looks like this issue:

Filter ||a2z.com^ breaks Alexa-Devices · Issue #808 · AdguardTeam/AdGuardSDNSFilter

The ||a2z.com^ filter (via easy privacy) causes Alexa devices to stop working. avs-alexa-14-eu.amazon.com blocked by CNAME:

github.com

If it is this filter that causes the problem, then AdGuard has to whitelist the mentioned adresses. Otherwise i can‘t use AdGuard until Theres another fix. I‘m using AdGuard configured in my router with standard Servers and DoT. So i can’t configure anything. Just use another service…

 

[Blaz]

I opened a pull request to whitelist the url, just have to wait for my colleagues.

 

[Julien]

Thank you,
I am on a centos and I do not see anything blocked in the events. I have already added this to my whitelist.

@@||amazon.fr^
@@||amazon.com^
@@||mads.amazon-adsystem.com^

even with @@||a2z.com^ it doesn't work.

 

[Boo Berry]

Whitelisting will only work if you're using AdGuard Home or AG for Windows/Mac/Android with DNS filters. AdGuard DNS itself will need first the AdGuard DNS filter updated with the fix merged and then on the server-side AdGuard DNS will have to update the AG DNS filter it uses for it to start working again for AdGuard DNS users.

AdGuard DNS users could switch to the AdGuard DNS non-filtering server to fix it in the meantime, but know it doesn't block ads.

 

[Julien]

i'm using AdGuard Home v0.106.3.
but the whitelist does not change anything. I restarted the server, cleaned the DNS cache, and restarted my Alexa.

 

[Onslaught]

AdGuard DNS users could switch to the AdGuard DNS non-filtering server to fix it in the meantime, but know it doesn't block ads.

that‘s why i’ve switched to DNSforge in the meantime until its fixed. DNSforge blocks ads too.

 

[Boo Berry]

i'm using AdGuard Home v0.106.3.
but the whitelist does not change anything. I restarted the server, cleaned the DNS cache, and restarted my Alexa.

Add

@@||a2z.com^$important

to the custom filtering rules, and that should fix it. You have to add the $important modifier to the rule to get it to work and override the existing rule in the DNS filter.

 

[Julien]

good, well tried but it still does not work.

 

[Julien]

finally, I changed the DNS for Alexa in my DHCP. Thanks for your help. I will wait for the correction.

 

[Blaz]

Fix should be available on DNS in a few hours (possibly already syncronized).

 

[Julien]

Thanks for your feedback. I'll try when I get home this evening. Good day.

 

[Julien]

I connected an Alexa and it works. Thank you.