Jump to content
IGNORED

Google DNS vs Cloudflare DNS for Tidal Qobuz


Recommended Posts

In the last few days I've been diagnosing a Tidal issue with a user in Romania.  With Google DNS, Tidal works for his home setup and work setup.  With Cloudflare DNS, Tidal at home is slow (takes more than 10 seconds for a seek) but it's normal at work.  Of course his home ISP and work ISP are different.

 

We went through changes from Google DNS -> Cloudflare DNS -> Google DNS -> Cloudflare DNS -> Google DNS, and tested more than one hardware units.  The result is 100% consistent, i.e. the problem 100% occurs with Cloudflare DNS, and 100% works well with Google DNS.

 

Anyone has any insights to share about this, or what could possibly go wrong with his home ISP, or what he should tell his home ISP?

 

P.S. I've read a competitor streamer support post that recommends Google DNS for US, and Cloudflare DNS for Europe.

Peter Lie

LUMIN Firmware Lead

Link to comment

If I might make make a suggestion - utilize something like Pingplotter as that can actually graph and list out where your problems are. This way you can test the different DNS servers. 

 

image.thumb.png.5b8e92638077251907476360f0b5105a.png

Current:  Daphile on an AMD A10-9500 with 16 GB RAM

DAC - TEAC UD-501 DAC 

Pre-amp - Rotel RC-1590

Amplification - Benchmark AHB2 amplifier

Speakers - Revel M126Be with 2 REL 7/ti subwoofers

Cables - Tara Labs RSC Reference and Blue Jean Cable Balanced Interconnects

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...