02-10-2025 06:01 PM
So my SH Pro finally updated last so i have changed the DNS on the router to Cloudfare however using dnschecker.tools the hub still uses BT DNS servers 😞 . Hub and extender have been rebooted since DNS was changed.
Anyone else getting this also?
| PASS | PASS | PASS |
| FAIL | FAIL | FAIL |
| FAIL | FAIL | FAIL |
| FAIL | FAIL | FAIL |
However if i manually set them on the network adapter it works properly, so does the Hub still secretly use BT DNS also even though you set it to No?
| PASS | PASS | PASS |
| PASS | PASS | PASS |
| PASS | PASS | PASS |
| PASS | PASS | PASS |
04-10-2025 11:38 AM
Did you renew the DHCP lease of the device you tested from after making changes in the hub?
The custom DNS feature on the EE hubs does not change the DNS resolvers assigned to the WAN connection of the router. Instead it modifies the DHCP server to issue your custom DNS addresses as part of the DHCP lease when a device establishes a connection to the hub (similar to you explicitly configuring DNS on the network adapter).
04-10-2025 12:43 PM
The PC i was using to test has a static IP assigned at the router.
I just dont see why the BT DNS servers still show up, if the router has assigned the Cloudfare DNS to the PC but why when checking do BT show up when set as auto, however on same PC if i manually assign Coudfare DNS at network adapter everything passes perfect and no BT DNS?