- This topic has 934 replies, 99 voices, and was last updated 6 years, 11 months ago by
.
-
Posts
-
3rd time lucky with the factory reset/wait 1 hour.
Now working, with DHCP and isp DNS servers.
good one Rocksta..
One change I did make, was on the router for DHCP server, changing first DNS server from DNS relay (i.e. the router address) to ISP assigned DNS server.
Rocksta – 1 hour ago »
3rd time lucky with the factory reset/wait 1 hour.
Now working, with DHCP and isp DNS servers.
Did you notice any differences from your previous attempts? For instance, you mentioned before that it hadn’t gone to the Home screen after reset – did it do so this time? And you then pressed Exit?
JamesB – 2 minutes ago »
Rocksta – 1 hour ago »
3rd time lucky with the factory reset/wait 1 hour.
Now working, with DHCP and isp DNS servers.
Did you notice any differences from your previous attempts? For instance, you mentioned before that it hadn’t gone to the Home screen after reset – did it do so this time? And you then pressed Exit?
This is the same instance of reset in which I mentioned that, so no, it had not gone to Home page. It went to the channel previously being viewed, and I pressed Exit there, but nothing happened i.e. it stayed on the channel.
Mystery. But good that you’ve got it working again.
Maybe Freesat changed the address of their servers, but my router had the old address cached.
Ignore that – my other box was working.
A mystery!
Rocksta – 51 minutes ago »
Maybe Freesat changed the address of their servers, but my router had the old address cached.
A router does not cache DNS addresses. The DNS server does but would return the same address to both units.
Any service provider would not just change a servers ip address, unless they also continued the service on the old server for 24 hours.
Note: it is possible for some professional routers to run a DNS application.
Edit: Please let us know if it continues working over the next few days.
REPASSAC – 24 minutes ago »
A router does not cache DNS addresses.
…
Edit: Please let us know if it continues working over the next few days.
Routers do cache addresses, it’s a core function (see dns cache poisoning attacks), and your PC or other networked device has its own cache too. Anyway, I did say ignore that as my other Humax box was working. Perhaps the new s/w of the HDR1000S does not like local DNS addresses used in DNS relay.
Does anyone know the rationâle for waiting an hour after the reset?
I’d imagine they’ve changed the ttl ‘time to live’ down to an hour or less for their dns entries, i.e. time the client should wait before checking/renewing dns.
If it were previously 1 day then it would take 24 hours which may explain their older advice of leaving it overnight.
Freesat do seem to be struggling though, I assume users are being tracked so maybe a mixture of stale/invalid session id’s and/or invalid dns.
If it is a indication that they think the problem is fixed, freesat have removed their link to the problem.
JamesB – 9 hours ago »
Does anyone know the rationâle for waiting an hour after the reset?
Data is transmitted along with freesat programmes to, for example, control the red button, register new channels arriving and to record showcase entries. I imagine the hour is to pickup this and perhaps other data.
damian, they would need to wait for a whole day after such a change for ISP’s cached entries to become stale. Most production service providers would route packets at their end. That way they can make instant changes when necessary.
Rocksta, Domestic routers (but those running DD-WRT can install a DNS server) but otherwise do not cache entries which PC’s do, they forward requests to the WAN’s DNS. The article I found (Wikipedia) for your keywords refers to a DNS cache. What commends on your router enable your DNS cache to be managed?
REPASSAC – 1 hour ago »
If it is a indication that they think the problem is fixed, freesat have removed their link to the problem.
Fingers crossed
REPASSAC – 4 hours ago »
damian, they would need to wait for a whole day after such a change for ISP’s cached entries to become stale.
Rocksta, What commends on your router enable your DNS cache to be managed?
If the ttl were 24 hours and freesat changed ttl to one hour, and the emphasis is on ‘if’, then it would take 24 hours for that initial change to propogate so initially they’d be asking users to wait 24 hours, then after the change had been propogated one hour should be enough. None of us know for sure what freesat have been up to, but I’d imagine that they changed the ttl amongst other stuff. Whether freesat have the ability to re-route at their end is debatable, they seem to have struggled thus far.
On my domestic router to clear the dns I use the command ‘multid -s’ to stop the service, and ‘multid’ to start it. I’d have to telnet/ssh to the router and there’s no GUI command in common with most routers. On other domestic routers, dlink etc the command ‘disable auto DNS’ etc. etc.. The majority of routers are locked down and at most just have a basic web GUI so the only effective way to flush dns is to reboot the router. This has little effect though if the ISP’s dns is wrong. It’s quite possible that 901/903 would work and showcase not if dns were wrong.
On a windows machine you’d use the ‘ipconfig /flushdns’ or similar at an elevated, if necessary, command prompt. There will be a command on the hdr1000s, but as it’s locked down nobody can use it or diagnose problems which then forces users to reset and wait in hope/vain.
It’s also possible that it takes an hour to populate the box with the necessary data or updated data is transmitted hourly or more regularly than previously. Who knows for sure?
We’re up to page 56 now and I still reckon this could have been diagnosed by page 2 if freesat hadn’t have locked down the box
- You must be logged in to reply to this topic.