@camelus 

 

On the Internet settings for the router you should see DNS, you can set them there and save it.

 

However, this make NO SENSE to me?

 

DNS is the Domain Name Server. It translates the 'english' site (like www.CNN.com) to the sites IP Address.

 

Now some say CloudFlare's DNS's are faster, and some are faster than others. However, if a device, be it a PC or Tablet, has defined the DNS it will use, the Router has NOTHING to do, it just processes the packets. All packets have an IP Address in it, they do not have to ask the Router to 'translate' it.

 

Only thing you'll accomplish by changing the Router's DNS settings is what the router will use WHEN it needs to translate a sites IP Address. It will NOT help you at all.

 

I suspect there are other problems and it is not the DNS.

 

Might want to look at this, https://www.cloudflare.com/learning/dns/what-is-dns/

 

I could be wrong though as I don't think this is a DNS or router problem? You could possibly find more Googling the Music Streamer name with problems, or locate a FORUM for it on the vendor's site?

@IrvSp 

 

Thanks for the message!

 

Now it's even clearer that the ISP has a problem, not with the device.

I've tried another unit on my home network and it has the same behavior. 

More than this, I have tried my device on a different network with a different ISP...everything works as it should...

So everything leads to a ISP problem with Google DNS instead of now accepted by the unit's firmware, Cloudflare DNS.

 

 

@camelus 

 

Still doesn't make sense to me?

 

What I suspect is the Streamer vendor changed the IP Address it is going too.

 

Again, if the device has its OWN DNS, packets are sent out to go to a specific IP Address. If a 'name' is used, the router will use the DNS it has, either specified internally by you in the router, or use the ISP's designated DNS it gets from the ISP.

 

You stating the Streamer has its own DNS so the problem then lies in 'getting to that IP Address'.

 

You've basically determined that your ISP is the problem. Another ISP it works on.

 

Fine, but that would indicate to me that the ISP is BLOCKING that IP Address?

 

You never mentioned if you got any error messages either? I'll assume you don't know where the Streamer is trying to go? A program could capture that but Support would need to help with that with special f/w on the router.

 

Before looking at the ISP as the problem, I'd still go back to the Streamer vendor. What did THEY change? I can't think a DNS internal change would cause this problem because if the DNS they are using produces an IP Address that your specific ISP has blocked, they, the Streamer vendor, would need to fix this.

 

Calling the ISP and telling them their DNS is broke is wrong, telling them they are blocking an UNKNOWN IP Address isn't going to help. You need that specific IP Address. If the Streaming Vendor gave you wrong info on it changed the DNS, you'll need the NAME of the site they are trying to go to.

You ISP will NOT take your word for it I'd bet too. You Streaming Vendor they would listen too.

 

That is my take on this. Bottom line, you need more information such as vendor s/w change, and where the Streamer is trying to go to. Me, I'd still be working with the Streaming vendor and supply the info you discovered.

@IrvSp 

 

thank you again for the reply.

the stem reader manufacturer told me that the only modification they made on the new firmware is that the new one is using Cloudflare DNS while the previous firmware used Google DNS.

 

Thats all...

Except me, nobody reported this type of issue.

 

There is no error to display, the only problem is that the time spent while skipping from a track to another rises from 2-3 seconds to 12-15 seconds. I find this annoying....

 

camelus wrote

There is no error to display, the only problem is that the time spent while skipping from a track to another rises from 2-3 seconds to 12-15 seconds. I find this annoying....

@camelus 

 

Ahh, so there is no 'DNS' or ISP problem. Well, there could be. Depends on how 'long' it takes you to reach the DNS...

 

For instance, using PING:

 

==============

C:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=19ms TTL=115
Reply from 8.8.8.8: bytes=32 time=19ms TTL=115
Reply from 8.8.8.8: bytes=32 time=19ms TTL=115
Reply from 8.8.8.8: bytes=32 time=20ms TTL=115

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 20ms, Average = 19ms

C:\>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=15ms TTL=56
Reply from 1.1.1.1: bytes=32 time=16ms TTL=56
Reply from 1.1.1.1: bytes=32 time=15ms TTL=56
Reply from 1.1.1.1: bytes=32 time=16ms TTL=56

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 16ms, Average = 15ms

=============

 

On my ISP (Spectrum), I do get to CloudFlare faster.

 

Using TRACERT to find the number of hops:

 

===================

C:\>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  TP-SHARE [192.168.0.1]
  2     9 ms     9 ms    10 ms  072-031-136-121.res.spectrum.com [72.31.136.121]
  3     9 ms    10 ms     9 ms  071-046-009-181.res.spectrum.com [71.46.9.181]
  4     9 ms     8 ms     9 ms  bundle-ether33.orld71-car1.bhn.net [72.31.195.146]
  5    13 ms    14 ms    14 ms  bu-ether44.tustca4200w-bcr00.tbone.rr.com [66.109.6.128]
  6    20 ms    19 ms    19 ms  0.xe-11-3-3.pr0.dca10.tbone.rr.com [66.109.1.32]
  7    20 ms    20 ms    19 ms  209-18-36-59.tbone.rr.com [209.18.36.59]
  8    19 ms    18 ms    18 ms  209.85.252.161
  9    19 ms    19 ms    19 ms  108.170.225.127
 10    19 ms    19 ms    18 ms  dns.google [8.8.8.8]

Trace complete.

C:\>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  TP-SHARE [192.168.0.1]
  2     8 ms     8 ms     9 ms  072-031-136-121.res.spectrum.com [72.31.136.121]
  3     8 ms     9 ms     8 ms  ten-0-5-1-6.orld35-ser1.bhn.net [72.31.223.44]
  4    10 ms    11 ms    10 ms  bundle-ether33.orld71-car1.bhn.net [72.31.195.146]
  5    15 ms    14 ms    14 ms  0.xe-2-2-1.pr0.atl20.tbone.rr.com [66.109.9.138]
  6    27 ms    47 ms    16 ms  66.109.5.131
  7    21 ms    20 ms    20 ms  66.109.1.243
  8    16 ms    15 ms    15 ms  one.one.one.one [1.1.1.1]

Trace complete.

===============

 

2 less hops to CloudFlare.

 

Your results could be different.

 

Also, I don't know how many different accesses to the DNS have to be made?

 

Still, I don't think this is an ISP problem?