Hifiman000 Posted August 18, 2021 Share Posted August 18, 2021 I put in a multi zone outdoor control 4 audio streaming system almost 2 months ago. Now I can't stream Tidal or Spotify. It just cuts in and out every few seconds. I've rest the router and the EA3 multiple times and it doesn't fix it. Any suggestions? Quote Link to comment Share on other sites More sharing options...
mstafford388 Posted August 18, 2021 Share Posted August 18, 2021 Check your DNS and make sure it's not using crappy cable company DNS. Quote Link to comment Share on other sites More sharing options...
LollerAgent Posted August 19, 2021 Share Posted August 19, 2021 2 hours ago, mstafford388 said: Check your DNS and make sure it's not using crappy cable company DNS. DNS could affect launching the stream initially, but it should not affect a single stream cutting in/out. Quote Link to comment Share on other sites More sharing options...
lippavisual Posted August 19, 2021 Share Posted August 19, 2021 10 hours ago, LollerAgent said: DNS could affect launching the stream initially, but it should not affect a single stream cutting in/out. It certainly can if the address doesn’t resolve quick enough, which is what many ISP’s provide. This will cause the cutouts and/or buffering. safe bets are to configure your router and dhcp scope to always use any of the following: 8.8.8.8 8.8.4.4 1.1.1.1 msgreenf 1 Quote Link to comment Share on other sites More sharing options...
LollerAgent Posted August 19, 2021 Share Posted August 19, 2021 1 hour ago, lippavisual said: It certainly can if the address doesn’t resolve quick enough, which is what many ISP’s provide. This will cause the cutouts and/or buffering. safe bets are to configure your router and dhcp scope to always use any of the following: 8.8.8.8 8.8.4.4 1.1.1.1 There is a reason though that the stream stopped in the first place, and that isn't DNS. DNS can potentially cause the stream to fail (or be slow) to reconnect in *some* cases (depending on the streaming implementation, the TTL's on their DNS records and the client-side caching capability of your local device and/or router). Quote Link to comment Share on other sites More sharing options...
mstafford388 Posted August 19, 2021 Share Posted August 19, 2021 20 minutes ago, LollerAgent said: There is a reason though that the stream stopped in the first place, and that isn't DNS. DNS can potentially cause the stream to fail (or be slow) to reconnect in *some* cases (depending on the streaming implementation, the TTL's on their DNS records and the client-side caching capability of your local device and/or router). I have absolutely seen DNS issues to cause streaming services to cut in and out. Quote Link to comment Share on other sites More sharing options...
LollerAgent Posted August 19, 2021 Share Posted August 19, 2021 8 hours ago, mstafford388 said: I have absolutely seen DNS issues to cause streaming services to cut in and out. Because the DNS server sent you to a CDN edge location that was geographically distant from your client (thus inducing latency)? What exactly was the DNS issue that you're describing? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.