01-07-2025 07:58 PM
The latest f/ware updated SH+'s allow you to config your own DNS instead of using EE's or does it?
My f/ware today updated to version r3.8.11-R-1414606-PROD-83002 & the ability to not have AUTO DNS Servers but to config your own appeared under Advanced Settings > My Network. So I set them to OpenDNS (208.67.222.222 & 208.67.220.220). Browsing & suchlike still works.
However the page Advanced > BB > Internet still shows the BT servers:
Broadband primary DNS: 81.139.56.100
Broadband secondary DNS: 81.139.57.100
So which set of DNS is the router using?
(I did reboot router in between so that changes take effect as it advised.)
I've only just had this f/ware update. I dunno when configurable DNS 1st appeared in the f/ware updates. Anybody remember?
Solved! See the answer below or view the solution in context.
02-07-2025 11:38 AM
@XRaySpeX The whole returned table so you can compare what your's does.
PASS | PASS | PASS |
PASS | PASS | PASS |
PASS | PASS | PASS |
PASS | PASS | PASS |
02-07-2025 11:49 AM - edited 02-07-2025 11:51 AM
@XRaySpeX Try another DNS from the list below that should show, see what changes. Takes a couple to 30 seconds to fill all the tables below....
02-07-2025 05:23 PM
@XRaySpeX - you're comparing Apples with Oranges.
@XRaySpeX wrote:My f/ware today updated to version r3.8.11-R-1414606-PROD-83002 & the ability to not have AUTO DNS Servers but to config your own appeared under Advanced Settings > My Network. So I set them to OpenDNS (208.67.222.222 & 208.67.220.220).
Doing this is asking the hub to assign custom DNS server addresses as part of its DHCP offer i.e. when the hub issues a LAN IP to clients, it also issues the DNS addresses you have specified. If you were to run something like ipconfig from a connected Windows machine then you would see that the network interface has the custom DNS assigned. This means your connected devices are going 'straight to the source' for DNS requests, rather than proxying/forwarding them through the hub.
@XRaySpeX wrote:However the page Advanced > BB > Internet still shows the BT servers:
Broadband primary DNS: 81.139.56.100
Broadband secondary DNS: 81.139.57.100
These are the DNS addresses assigned to the PPPoE/WAN interface of the router. They are assigned by the RADIUS equipment out on the Broadband network. Any DNS requests your hub makes is using these resolvers.
@XRaySpeX wrote:So which set of DNS is the router using?
The router is using the BT/EE DNS; Your connected devices are using your custom DNS.
Assigning custom DNS via DHCP is probably the preferred method (rather than changing the hub's DNS) as it's removing a hop/point of failure from the mix.
02-07-2025 05:59 PM
@XRaySpeX @bobpullen Bob posted this on another post so ideally the uPnP is also good to go for the old port fwd fixing, "I've just posted in another thread that the latest firmware for SH31B seems to have fixed UPnP (3.8.11). It wasn't working prior to this."
02-07-2025 06:06 PM - edited 02-07-2025 06:16 PM
@bobpullen : Good thinking! I was forgetting that DNS were handed to clients as part of their DHCP request.
Yes, my PC's ipconfig does show OpenDNS as its DNS:
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
192.168.1.254
I'm sure when I checked this before it was only showing 192.168.1.254.
Thanks for solving this, @bobpullen , I was waiting for you to turn up.
02-07-2025 07:50 PM
As an aside, the hub shouldn't still be issuing its own IP as tertiary DNS server. Doubt it will cause too many problems in practice but suspect it's another bug that will need squashing in firmware.
02-07-2025 07:56 PM
@bobpullen wrote:
These are the DNS addresses assigned to the PPPoE/WAN interface of the router. They are assigned by the RADIUS equipment out on the Broadband network. Any DNS requests your hub makes is using these resolvers.
As a matter of interest, when is the router ever required to make a DNS lookup of itself? It's not like it is doing any browsing of itself; it is predominately handling packets. I can understand it if it had an Access Control feature to blacklist any websites by domain.
03-07-2025 06:55 AM
@XRaySpeX Wonder if it is anything to do with the Router and Parental controls, although it is all app managed the router still has to block at the setup times that are pre-programmed, there may be a lot going on under the hood and EE have felt that best way to deal is to always use and trust there DNS Servers.
03-07-2025 08:17 AM
@XRaySpeX wrote:As a matter of interest, when is the router ever required to make a DNS lookup of itself?
Couple of obvious ones I can think of: -