Sky Q and YouFibre - "Failed, Remote network problem.

[rit81]

Yes, but that's Sky's problem to sort out. It needs to work with every ISP / every DNS provider.

[Chodley]

---

@rit81 wrote:

Yes, but that's Sky's problem to sort out. It needs to work with every ISP / every DNS provider.

---

Depends what the problem is. Might not be in their control.

[rit81]

Of course it is! They are running an internet service. All it has to do is authenticate and then allow you to download.

All of the posters here with issues have no problems with their home internet on other websites; just sparidic issues with sky q downloading content.

[Chodley]

not all DNS services are as good as each other. Google's and Cloudflare's are usually recommended because they are so reliable but most ISPs ought to work just as well.

The wifi stack on the Q is a crock, I am sure of that. But that manifests itself as completely failed connections. This one seems to be more about finding and connecting to ad servers which via some ISPs seem fine and via others play up. It's very odd.

[AJT23]

I had this issue after moving to Rural Broadband from another point to point ISP. 

Changed the DNS to 1.1.1.1 and now catch up works. Its not 100% but pretty close. 

[Chodley]

What's a "point to point" ISP? I never heard the term before this thread and now that's twice 😄

[AJT23]

Point to point. No wires involved. It's a rural thing. I have a dish on my house that points to and connects to the service. My house is a mile from a road. BT service is 1mb/sec!

[Chodley]

---

@AJT23 wrote:

Point to point. No wires involved. It's a rural thing. I have a dish on my house that points to and connects to the service. My house is a mile from a road. BT service is 1mb/sec!

---

Ahh of course. Thanks.

[Andyboro1993]

I am still having same issues....nothing works. When my contract ends I'm cancelling Sky as I am not getting the service I pay for, had enough

[AJT23]

Did you do the dns change?

[rit81]

Guys, this talk of DNS is ridiculous. DNS is a hierarchical system of caching names to (mainly) IP addresses. If there is something wrong with a DNS entry it's up to the party supplying the service to make sure it works.

Of I was responsible for a website or service it's on me to make sure clients can access my services. That means making sure they can resolve via DNS the endpoints for my service.

The fact that this doesn't work all of the time is on Sky to investigate, if they do indeed "believe in better".

[Chodley]

We know what DNS is mate

Are you suggesting there's never been an issue with DNS propagation that affected one resolver more than another?

for some reason Sky's content delivery seems vulnerable to it because a number of people have found using google's or cloudflare's has fixed issues.

So yeah they should look into that, and as a punter with a problem you can wait, or you can try a workaround.

[rit81]

If there is a problem somewhere with customers accessing Sky's services, it's on them to investigate. That involves the full stack (ie including DNS). If there is a problem with customers resolving names, they need to figure out the root cause and work with whoever it is to fix the problem.

[Chodley]

Ok you are suggesting the "wait" option then. (Sorry if Inedited my post above while you were replying)

I think that might be sensible if you could get to someone in sky's engineering team that would understand what you were talking about but with a mass market product, that is usually very difficult. Otherwise, given it has literally zero downside, I prefer changing it.

Of course, it might not fix the problem anyway. Could be plenty of other things.

[rit81]

I'm suggesting that there is no way for us (Sky users) to fix this problem!

I have my router at home configured to use Google dns but still have this issue of failed downloads.