User Profile
EvilllKint
Neighbour
Joined 5 years ago
User Widgets
Contributions
Re: Telus WiFi Hub Arcadyan - Parental Control
Won't help, unless amirabdi is willing to manually set DNS on all their home devices. The Arcadyan/Wi-Fi hub will happily ignore any upstream DNS you feed it, and will instead push its own LAN IP as the only DNS for IPv4 clients via DHCP. Trying to use filtering DNS servers like CIRA DNS or CloudFlare for Families is pointless when using the Arcadyan hub as a DHCP server (which cannot be disabled, outside of setting it in Bridge mode). See my reply in this thread : https://forum.telus.com/t5/Internet-Home-Phone/Telus-Wifi-Hub-manual-DNS-not-working/m-p/121852#M301194.4KViews0likes0CommentsRe: Telus Wifi Hub manual DNS not working
I should add that using the Hub's built-in firewall or port forwarding feature in order to block/redirect DNS requests sent to the Hub's LAN IP does not work. There is truly no method to shut down that built-in DNS server or change its behaviour.16KViews1like0CommentsRe: Telus Wifi Hub manual DNS not working
That does not work. The TELUS Wi-Fi Hub will always have a DNS resolver running on its LAN IP, that DNS resolver will always bypass *any* upstream IPv4 or IPv6 DNS that you defined in its config (you have the right steps in your article), and finally the LAN IP of the Wi-Fi hub will always get pushed as the primary DNS server by the built-in DHCP server. Basically, you can set *all* of your home devices with custom DNS settings in order to bypass the Telus Wi-Fi hub, or you can set the hub in Bridge mode and use another device as your ethernet + wifi router. I am exactly in the same boat as jcbshw here; TELUS Wi-Fi Hub LAN IP : 10.0.2.1 Pi-Hole DNS : 10.0.2.10 I set 10.0.2.10 as *both* the WAN DNS and the LAN DNS, I save the config, reboot the TELUS Wi-Fi Hub, reboot all my client devices. Every single Windows computer in the house, and gaming console will always get 10.0.2.1 pushed as its *only* IPv4 DNS, every time, effectively bypassing my Pi-Hole DNS. Oddly, this does not apply for IPv6 cliients, however not all of my home devices can do IPv6-only. Simple dig commands run from any computer on my home LAN show that my findings are correct : Querying my Pi-Hole DNS : dig @10.0.2.10 pornhub.com +short 0.0.0.0 Querying the TELUS Wi-Fi Hub DNS : dig @10.0.2.1 pornhub.com +short pornhub.com. 66.254.114.41 Querying Cloudflare's family DNS : dig @1.1.1.3 www.pornhub.com +short 0.0.0.0 In the example above, my Wi-Fi Hub has its WAN DNS set to cloudflare's 1.1.1.3 DNS, which *will* block pornhub.com every time. The Hub entirely bypasses its own DNS config and gladly fetches pornhub.com's A record from what I can only assume are Telus internal DNS hard-coded in its firmware. I consider this a bug, and sadly looking at my Wi-Fi Hub info page, I don't have a lot of hope for a firmware update that will fix the issue, as the versions below have not changed by a single release in the 2+ years I've had the Hub. Firmware Version: v3.00.21 build02 Boot Code Version: 0.00.01 Hardware Version: 0116KViews1like1Comment