Hi All,
Sorry for slow reply, been in hospital. I think I'm getting closer on this one, in the space of DNS rebind attack protection.
If you've not already, could you reach out to me with your Hub Serial Number and I can monitor for these events to see if it's the same.
Thanks
Steve
Hi Steve - I am experiencing the same issu with my SH2 on Full Fibre line - can you monitor my huib as well?
As said before I found I had an ethernet cable plugged in and the wifi on. Turning the wifi off stopped the problem happening again.
Will take a look 🙂
Whilst I know this thread has not been updated since the December 1st. I would like to add my mums hub into the mix here.
It works well then all of a sudden it fails to resolve DNS names. The Web pages report ERR_DNS_BAD_CONFIG
Manually changing the DNS on the PC to 1.1.1.1 or 8.8.8.8 resolves the issue and the PC is able to connect again.
Rebooting the hub resolves the issue, but for obvious reasons is not ideal as mum has been migrated to Digital Voice. Is there any firmware upgrade planned to address this issue?
Since BT still hasn’t fixed the intermittent DNS issue, I ended up building a workaround.
I put together a small project called Router Watchdog that automatically power-cycles the router if it loses internet.
It works like a dead man’s switch:
A Tasmota smart plug controls power to the router
The plug runs a local countdown timer
A small service on a cheap VPS resets that timer via MQTT every 15 minutes
If the router loses connectivity, the plug can’t receive the reset
The timer expires and the plug power-cycles the router
Because the timer runs locally on the plug, it still triggers even when the internet is down.
It’s not a fix for the root cause, but it’s stopped me having to manually reboot the router every time DNS drops.
I’ve put it on GitHub here:
[mod edit: third party link removed as community terms]
You’ll need a Tasmota smart plug and a basic VPS (mine costs about £2 per month).