26-01-2026 06:11 PM
I have a domain chryselwood.ca that I can't access using an EE broadband connection unless I use a vpn. I'm able to access the site on the mobile network with no issues. what am I missing?
27-01-2026 03:21 PM
I think DNS is largely irrelevant as both of your lookups (working and non-working) point to the same IP. All DNS is responsible for is 'converting' the domain name to an IP address. When pinging the IP address directly, it's not going anywhere near a DNS server.
Have you tried my suggestion of powering your hub off for a period of time to see if you can pick up a different IP address?
FWIW, I am also able to get to the site without difficulty.
27-01-2026 03:44 PM
I used to work in IT before I retired - when networking was "simple" ;). DNS - true. The address is valid and resolved. Another person helping is able to access it with no issues as I can on the mobile network. There are differences in the trace routes between the ones that work and mine that doesn't work. I should mention that it started working all of a sudden back in the summer (not due to anything I did - firmware update?) and all went well until I had to unplug the router sometime in the fall. It was so difficult getting someone on the phone at EE/BT with the skills to investigate that I just continued using the VPN approach as it worked. I'll try your suggestion when I take the dogs out for their pre-supper walk
27-01-2026 05:13 PM
hi - shutdown router for an hour - got new ip address - same gateway - same problem 😞
27-01-2026 05:18 PM - edited 27-01-2026 05:44 PM
FYI:
The DNS under IPv4 Config are those handed out to all connected devices under the DHCP lease & are used whenever those devices need a domain look-up, i.e. nearly all the time.
The DNS under BB > Net > TCP/IP Info are those used by the router itself for its own ends & are rarely needed for things like site Access Control.
However as @bobpullen observes the DNS don't really come into this problem as IPs are being looked-up correctly.