TELUS DNS Server Addresses, Settings, and Troubleshooting

If you're a TELUS internet subscriber in British Columbia or Alberta and pages are loading slowly, unknown domains are redirecting to a TELUS search screen, or DNS queries are failing intermittently, your resolver setup is the first thing to audit. This article covers TELUS's default DNS server addresses for IPv4 and IPv6, how to verify what your devices are actually querying, the most common TELUS-specific failure modes ranked by frequency, and exact steps to reconfigure DNS on every major gateway and device type.

TELUS Default DNS Server Addresses

TELUS assigns DNS resolvers automatically via DHCP on all residential and small business internet connections. The standard IPv4 addresses for TELUS's recursive DNS servers are:

Some connections — particularly TELUS Mobility LTE/5G accounts and legacy ADSL plans — may receive different addresses in the 64.175.x.x or 65.39.x.x ranges. These are still TELUS infrastructure. To confirm which server your device is actually querying:

If the output shows a private IP like 192.168.1.1, your router is acting as a DNS relay — forwarding queries upstream to TELUS on your behalf. That is normal and expected. To see the actual upstream resolver, log into your router's admin panel and check the WAN DNS settings.

IPv6 DNS on TELUS PureFibre

TELUS PureFibre and newer Fibre-to-the-Home connections are dual-stack by default, meaning devices receive both IPv4 and IPv6 addresses via DHCPv6. TELUS also assigns IPv6 DNS servers automatically on these connections. To check what IPv6 DNS your device received:

If you are manually overriding DNS, always configure both IPv4 and IPv6 resolver addresses. A device that prefers IPv6 will fall back to DHCPv6-assigned DNS — which will be TELUS's servers — even if you have set custom IPv4 DNS. All major third-party resolvers provide IPv6 addresses: Cloudflare at 2606:4700:4700::1111 and 2606:4700:4700::1001, Google at 2001:4860:4860::8888 and 2001:4860:4860::8844.

TELUS DNS Search Assist: What It Does and How to Disable It

By default, TELUS enables DNS Search Assist — an NXDOMAIN redirect feature. When a domain doesn't exist or a URL is mistyped, TELUS's resolvers return a forged A record pointing to a TELUS-hosted search results page rather than the standard NXDOMAIN (domain not found) error. This behavior breaks several things in practice:

• Applications and scripts that rely on NXDOMAIN responses to detect whether a domain is real — common in split-horizon DNS environments and VPN configurations
• Pi-hole and other sinkhole-based ad blockers, which expect blocked domains to return NXDOMAIN rather than resolving to an IP
• VPN split-tunnel setups where NXDOMAIN signals that traffic should route through the tunnel
• Browser developer tools and monitoring agents that parse DNS error types for retry logic

To disable DNS Search Assist: log into your TELUS My Account at telus.com, navigate to Internet > Advanced Settings > DNS Search Assist, and switch it off. If this option is not visible in your account tier, contact TELUS support and reference the phrase "NXDOMAIN redirect opt-out." Alternatively, switching to any third-party resolver completely bypasses the feature, since the redirect is implemented server-side on TELUS's resolvers only.

Common TELUS DNS Problems, Ranked by Frequency

1. NXDOMAIN Redirect (DNS Hijacking)

The most frequent complaint from TELUS subscribers: mistyped URLs or legitimately unreachable domains land on a TELUS Search Assist page instead of returning a browser error. Fix: disable via My Account as described above, or switch resolvers entirely. If you are seeing this for a domain that should exist, verify the domain is registered and has valid NS records using the DNS Lookup tool before assuming TELUS is at fault.

2. Elevated DNS Query Latency

TELUS's recursive resolvers are centralized rather than anycast-distributed, which means customers in rural BC, the Interior, northern Alberta, or any region geographically distant from a TELUS resolver POP may experience DNS query times of 40–80ms. This adds up on modern web pages that resolve dozens of unique hostnames per load. Benchmark before deciding to switch:

If TELUS consistently scores 50ms or higher while Cloudflare or Google scores under 15ms from your location, switching resolvers will produce a noticeable improvement in perceived page load speed.

3. Optik TV or SmartHome Security Breaks After DNS Change

TELUS Optik TV uses internal TELUS hostnames in the telus.net and optik.tv zones that resolve only via TELUS's own DNS infrastructure. If you change your router's upstream DNS to a third-party resolver, Optik guide data, VOD, and catch-up TV may stop working. The cleanest fix is to set custom DNS on individual client devices only, leaving the router pointed at TELUS DNS. On routers running OpenWrt or DD-WRT, you can forward only the Optik-related zones to TELUS and route all other queries to your preferred resolver. In OpenWrt, add to /etc/config/dhcp:

DD-WRT supports the same dnsmasq syntax under Services > Services > Additional DNSMasq Options. This preserves Optik TV resolution while routing all other DNS to Cloudflare.

4. Intermittent SERVFAIL Responses

Random "server not found" errors that clear on page refresh typically indicate brief TELUS resolver instability or a routing event. Test both servers directly to isolate which one is affected:

If one returns SERVFAIL and the other resolves correctly, your primary resolver is temporarily degraded — the secondary should cover automatically. If both fail simultaneously, the issue is either your WAN connection or a broader TELUS infrastructure event. Check community forums and outage trackers for active TELUS reports.

5. Stale Cache Returning Outdated Records

After a domain's DNS records change — a site migration, a new hosting provider, an MX update — TELUS's resolvers cache the old records for the original TTL. If you need to see fresh records immediately, query a public resolver directly or query the authoritative nameserver:

Changing DNS on Your TELUS-Provided Gateway

TELUS deploys several gateway models depending on your service tier and installation year. The admin panel path varies slightly between them.

Arcadyan Wi-Fi Hub (current PureFibre residential deployments)

1. Open a browser to http://192.168.1.1. If that page does not load, try http://192.168.1.254 — some Arcadyan firmware revisions use this address. The label on the underside of the unit lists the actual default gateway IP.
2. Log in with the credentials printed on the unit label. The Wi-Fi password and admin password are unique per device on current TELUS hardware.
3. Navigate to Advanced > WAN > DNS Settings. The exact menu label varies by firmware generation — look for any item named DNS, WAN, or Internet Connection.
4. Switch DNS Mode from Automatic to Manual.
5. Enter your preferred Primary and Secondary DNS server addresses.
6. Click Save or Apply and wait 30 seconds for the change to propagate to connected devices.

Sagemcom FAST 5250 / 5655 (VDSL and FTTN connections)

1. Navigate to http://192.168.1.1 and log in.
2. Go to Advanced Setup > DNS.
3. Uncheck Use DNS proxy if you want devices to query your chosen DNS server directly rather than routing through the router's relay.
4. Enter your DNS server addresses and save.

Third-Party Routers on TELUS (Your Own Hardware)

If TELUS's gateway is in bridge or DMZ mode and you're running your own router, configure DNS at the WAN level of your router:

• TP-Link (192.168.0.1 or tplinkwifi.net): Advanced > Network > Internet > DNS — switch from automatic to manual and enter IPs
• ASUS (192.168.1.1 or asusrouter.com): WAN > Internet Connection > WAN DNS Setting — set "Connect to DNS Server Automatically" to No, enter addresses
• Netgear Orbi (orbilogin.com): Advanced > Setup > Internet Setup > Domain Name Server (DNS) Address
• Linksys (192.168.1.1 or linksyssmartwifi.com): Connectivity > Internet Settings > IPv4 — Static DNS 1 and Static DNS 2 fields
• Ubiquiti UniFi: Networks > [your LAN] > Advanced > DHCP Name Server > Custom — entered IPs will be pushed to all DHCP clients automatically

Changing DNS Per Device

Windows 11 / 10

1. Settings > Network & Internet > select your active connection > Hardware properties
2. Click Edit next to DNS server assignment > Manual > enable IPv4
3. Enter Preferred DNS and Alternate DNS
4. For encrypted DNS: set the DNS over HTTPS dropdown to On (automatic template) — this works with Cloudflare 1.1.1.1 and Google 8.8.8.8 out of the box

macOS Sequoia / Sonoma / Ventura

1. System Settings > Network > select the interface > Details > DNS tab
2. Click + to add server IPs. Remove the DHCP-assigned entries.
3. Click OK then Apply.

Linux with systemd-resolved (Ubuntu 20.04+, Fedora, Arch)

On systems without systemd-resolved (Debian minimal, Alpine), edit /etc/resolv.conf directly — but be aware that NetworkManager or dhclient may overwrite this file on reconnection. Use your distribution's network configuration tooling to set DNS persistently instead.

iOS 17 / 18

1. Settings > Wi-Fi > tap the (i) next to your network name
2. Configure DNS > Manual
3. Remove the existing DHCP-assigned entries, tap Add Server, enter your preferred IPs

For system-wide encrypted DNS on iOS that covers both Wi-Fi and cellular, install a DNS configuration profile (.mobileconfig) from Cloudflare or NextDNS. This enforces DoH across all apps, not just Safari.

Android 9 and Later

1. Settings > Network & Internet > Advanced > Private DNS
2. Select Private DNS provider hostname
3. Enter one.one.one.one for Cloudflare or dns.google for Google

Android's Private DNS feature uses DNS-over-TLS on port 853 and requires a hostname, not an IP address. TELUS does not publish a DoT hostname for their resolvers, so this mode is only usable with third-party providers. It applies system-wide across all apps and both Wi-Fi and mobile data connections.

Alternative Resolvers Worth Considering

TELUS DNS is adequate for basic browsing. Consider replacing it if you need accurate NXDOMAIN responses, encrypted DNS transport, lower query latency, or per-device query logging:

• Cloudflare (1.1.1.1 / 1.0.0.1) — consistently lowest query latency globally, strong privacy policy, full DoH and DoT support, free. IPv6: 2606:4700:4700::1111 / 2606:4700:4700::1001
• Google Public DNS (8.8.8.8 / 8.8.4.4) — excellent uptime and very fast from Metro Vancouver and Calgary, full DoH and DoT. IPv6: 2001:4860:4860::8888 / 2001:4860:4860::8844. See the Google Public DNS documentation for setup guides across all platforms.
• OpenDNS (208.67.222.222 / 208.67.220.220) — built-in content filtering categories; useful for offices and households wanting basic controls without separate software
• NextDNS — per-account resolver with query logging, custom blocklists, and DoH/DoT. Functions like a hosted Pi-hole. Free tier covers most households.

Confirming the Fix Worked

Preventing DNS Problems From Recurring

• Set DNS at the router level so all new devices on the network inherit it automatically — but remember the Optik TV caveat and use the domain-forwarding technique if needed
• Use resolvers from two different providers for primary and secondary (e.g., 1.1.1.1 and 8.8.8.8) so a single-provider outage does not take you down
• On Linux servers, pin /etc/resolv.conf using your distro's network manager to prevent DHCP from overwriting manual settings after reboots
• In 2026, enable DoH at the browser level (Firefox, Chrome, and Edge all support it natively under Privacy or Network settings) as a supplement — this encrypts DNS for browser traffic independent of your OS or router settings and prevents ISP-level DNS inspection regardless of which resolver you're using

Common Misdiagnoses

"TELUS is blocking this site." TELUS participates in Canada's voluntary and court-ordered website blocking framework administered by CRTC orders. Domains subject to blocking return NXDOMAIN from TELUS DNS but resolve correctly on 1.1.1.1 or 8.8.8.8. If a domain resolves on public resolvers but not on TELUS, a blocking order may be in effect.

"My DNS server is 192.168.1.1." That is your router acting as a DNS relay, not the actual resolver. Your router queries TELUS on your behalf. The real upstream server is visible in your router's WAN DNS settings page.

"Slow DNS explains my slow internet." DNS latency only delays the very first connection to each new hostname. Once an IP address is cached locally, DNS adds zero time to subsequent requests to that server. If repeat visits to familiar sites are slow, DNS is not the issue — look at throughput, routing, or the server itself.

"Flushing the router cache will fix stale DNS." Rebooting your router only clears the router's local DNS relay cache. Your devices maintain their own DNS caches, and TELUS's upstream resolvers maintain theirs independently. To clear all layers: flush your device's DNS cache (commands above), flush your browser's cache, and if needed, query TELUS's servers directly with dig +nocache to bypass the resolver-side cache.

2026 Notes: Encrypted DNS and DNSSEC on TELUS

As of mid-2026, TELUS's recursive resolvers validate DNSSEC for signed zones — querying a DNSSEC-signed domain against 205.210.42.205 with the +dnssec flag will return RRSIG records and the ad (authenticated data) flag in the response header. However, TELUS does not expose a public DNS-over-HTTPS or DNS-over-TLS endpoint. Queries between your device and TELUS's resolvers travel in plaintext UDP or TCP on port 53, meaning your ISP and any on-path observer can log all DNS activity.

If DNS query privacy matters for your use case — remote workers, small business with sensitive research activity, or households wanting to prevent ISP profiling — configure DoH or DoT at the device level using Cloudflare or Google resolvers as described above. Both support encrypted transport on all modern platforms. The underlying DNS protocol that governs how all of this works, including the message format TELUS and every other resolver implements, is defined in RFC 1035 — the 1987 specification that still underpins the entire DNS system.