If you're a SaskTel internet customer in Saskatchewan and your browsing feels sluggish, certain sites won't resolve, or you've just swapped in a new router and need the right settings, this page has what you need. Below are SaskTel's DNS resolver addresses, step-by-step configuration for every major platform, CLI verification commands, and a ranked list of the most common failure modes — starting with the fix, not the theory.
SaskTel DNS Server IP Addresses
SaskTel (Saskatchewan Telecommunications) operates two recursive DNS resolvers for residential and business internet customers. These are the servers your devices query to translate domain names into IP addresses every time you open a browser or app:
Both servers sit inside SaskTel's own IP block (ASN 6327), which means round-trip query times from within Saskatchewan typically stay under 5 ms — far lower than routing to a geographically distant public resolver. The secondary server exists purely for redundancy: if the primary is unreachable, your device automatically falls through to it without any visible interruption. Under normal conditions you have no reason to switch away from these.
SaskTel does not currently publish a dedicated IPv6 DNS resolver address in its public-facing customer documentation. If your modem is handing out an IPv6 DNS server via DHCPv6 or Router Advertisement, you can find it using the verification commands in the next section. For dual-stack environments, the two IPv4 addresses above handle the majority of queries and the IPv6 DNS address (when present) handles AAAA lookups on IPv6-preferred devices.
Find Your Currently Active DNS Servers
Before changing anything, confirm which DNS servers your devices are actually using. This rules out misconfigured software, a VPN client, or a router that's already forwarding to the right place.
Windows 10 / 11
macOS (Ventura, Sonoma, Sequoia)
Linux — systemd-resolved (Ubuntu 18.04+, Debian 10+)
Linux — legacy resolv.conf
If those commands already show 208.75.76.3 and 208.75.76.4, your modem is correctly advertising SaskTel's resolvers via DHCP and no manual configuration is needed. If you see a private IP like 192.168.1.1 or 10.0.0.1, that's your router acting as a DNS forwarder — the DNS change needs to be made in the router admin panel, not on individual devices.
Configure DNS at the Router Level
Changing DNS on the router means every device on your network — phones, smart TVs, laptops, everything on Wi-Fi — automatically uses the correct servers. This is almost always preferable to per-device configuration.
Access your router's admin panel using the URL that matches your hardware:
- SaskTel-supplied modem/router (Actiontec, Arris, Hitron): http://192.168.0.1 or http://192.168.1.1
- TP-Link: http://tplinkwifi.net or http://192.168.0.1
- ASUS: http://asusrouter.com or http://192.168.1.1
- Netgear Orbi: http://orbilogin.com
- Netgear (non-Orbi): http://routerlogin.net or http://192.168.1.1
- Linksys: http://linksyssmartwifi.com or http://192.168.1.1
- Xiaomi/Mi: http://miwifi.com or http://192.168.31.1
Inside the admin panel, look for WAN Settings, Internet, or Advanced → DNS depending on firmware version. You'll see fields labeled Primary DNS and Secondary DNS (sometimes DNS 1 / DNS 2). Set them to 208.75.76.3 and 208.75.76.4 respectively. Save and reboot.
OpenWrt: Edit /etc/config/network. Under your WAN interface block, add or update:
Apply with:
DD-WRT: Navigate to Setup → Basic Setup → Network Address Server Settings (DHCP). Set Static DNS 1 to 208.75.76.3 and Static DNS 2 to 208.75.76.4. Scroll down and click Save, then Apply Settings.
Configure SaskTel DNS Per-Device
If your router is managed by someone else or you need device-specific DNS settings for a particular machine, here is how to configure each platform directly.
Windows 10 / Windows 11
Open Settings → Network & Internet → Ethernet (or Wi-Fi). Click your active connection, then click Edit next to IP assignment. Switch to Manual, toggle IPv4 on, fill in your current IP and gateway (find these by running ipconfig), and set Preferred DNS to 208.75.76.3 and Alternate DNS to 208.75.76.4. Click Save.
Legacy path: Control Panel → Network and Sharing Center → Change adapter settings → right-click adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → select Use the following DNS server addresses and enter the IPs.
macOS
Open System Settings → Network → click your active connection → Details → DNS tab. Click + and add 208.75.76.3, then click + again and add 208.75.76.4. Remove any stale entries. Click OK, then Apply.
Ubuntu / Debian (systemd-resolved)
Set or uncomment these lines:
Restart the resolver:
iOS (iPhone / iPad)
Settings → Wi-Fi → tap the (i) icon next to your network name → Configure DNS → Manual. Delete any existing entries, tap Add Server and enter 208.75.76.3, tap Add Server again and enter 208.75.76.4. Tap Save in the top-right corner.
Android
The exact path varies by manufacturer. General route: Settings → Network & Internet → Wi-Fi → long-press your network name → Modify network → Advanced options → IP settings → Static. Enter your current IP address, prefix length (usually 24), and gateway, then set DNS 1 to 208.75.76.3 and DNS 2 to 208.75.76.4. Save.
On Android 9 and later, Settings → Network & Internet → Private DNS lets you enter a DNS-over-TLS hostname. SaskTel does not operate a public DoT endpoint, so leave this on Automatic unless you specifically want to use a third-party encrypted resolver.
Verify the Configuration Is Working
After any change, flush the DNS cache and test by querying the resolvers directly from the command line.
Windows
macOS
Linux
A working resolver returns a valid IP address for google.com in under 10 ms. If you get SERVFAIL, NXDOMAIN on a domain that clearly exists, or the query times out entirely, the resolver may be down or there is a routing problem between your connection and SaskTel's DNS infrastructure.
To measure latency specifically:
Under 10 ms is normal within SaskTel's network. Anything consistently over 100 ms warrants investigation of the path between you and the resolver.
Also confirm which DNS server is handling your default queries without specifying one:
The Server: line should show 208.75.76.3 or your router's LAN IP (if the router is forwarding upstream to SaskTel).
Troubleshooting SaskTel DNS Problems
The following failure modes are ranked from most to least common among SaskTel internet customers.
1. Slow Resolution Despite Correct Settings
The most common cause is the router holding a DHCP lease with stale DNS data from a previous session. Force a DHCP renew before doing anything else:
On macOS: System Settings → Network → [interface] → TCP/IP → Renew DHCP Lease. If the router itself has stale resolver cache data, a 30-second power cycle clears it at the hardware layer.
2. NXDOMAIN for Sites That Clearly Exist
Run nslookup google.com without specifying a server. The Server line shows which resolver is actually answering. If it shows 127.0.0.53 (systemd-resolved stub), 127.0.0.1, or an unexpected private IP, trace the DNS chain back to the router — something upstream is overriding SaskTel's resolvers. If the resolver really is 208.75.76.3 and you're still getting NXDOMAIN for legitimate domains, check whether your SaskTel account has DNS-level content filtering active; some business plans include this at the resolver layer.
3. Intermittent Failures — Works, Then Stops
This pattern almost always traces to the router rather than SaskTel's infrastructure. Check for these specific conditions:
- Only one DNS server configured: If the primary becomes briefly unreachable and no secondary is set, every DNS query fails until recovery. Always configure both IPs.
- Router DNS cache overflow: Budget routers with small caches behave erratically when full. Disabling DNS caching on the router and letting devices query SaskTel directly often resolves this.
- DHCP lease expiry edge case: When the lease expires and the renewal request fails, the router may retain the old IP but drop its DNS configuration. A static WAN configuration eliminates this variable entirely.
4. SaskTel Resolver Completely Unreachable
During SaskTel network incidents, both 208.75.76.3 and 208.75.76.4 can become unreachable. Confirm with a direct ping:
If both time out but you can ping your default gateway, the problem is within SaskTel's network between your connection and their DNS infrastructure. Switch temporarily to a public resolver while waiting for the outage to clear:
5. DNS Hijacking — Wrong IPs Returned for Known Domains
If querying SaskTel's resolver returns obviously wrong addresses for major sites, something is intercepting DNS traffic. Possible causes: router firmware compromise, a rogue DHCP server on the LAN, or malware on the querying device. Verify by comparing the DNS server IPs shown in ipconfig /all or resolvectl status against what you configured — any mismatch is a strong indicator of active interference. Factory-reset the router if the admin panel shows DNS settings have been altered without your knowledge.
Common Misdiagnoses
The internet appears completely down. DNS failures look like total outages because browsers show generic connection error pages. The network itself is usually fine — only name resolution is broken. Confirm by pinging a known IP directly: ping 1.1.1.1. If that succeeds, the connection is up and DNS is the isolated problem.
One specific site is broken. If every other domain resolves correctly but one site fails, this is almost never a SaskTel DNS server problem. It is either a DNS propagation delay for that domain, a DNSSEC validation failure on that domain's zone, or the domain does not yet exist in the authoritative record. Check with an external lookup tool before calling your ISP.
A VPN broke DNS. VPN clients push their own DNS configuration to prevent leaks and bypass ISP resolvers. If DNS breaks immediately after connecting to a VPN, the VPN's own DNS servers are the active resolvers — not SaskTel's. Disconnect the VPN, re-test, and troubleshoot the VPN client's DNS settings separately.
When to Use a Third-Party Resolver Instead
SaskTel's resolvers handle the job for most residential use. Consider switching to a public resolver in these specific situations:
- You want encrypted DNS via DNS-over-HTTPS or DNS-over-TLS — SaskTel does not run a public DoH or DoT endpoint
- You need DNSSEC validation enforced at the resolver — Cloudflare 1.1.1.1 and Google 8.8.8.8 both validate DNSSEC by default
- You want DNS-layer malware and phishing blocking — Cloudflare 1.1.1.2 and OpenDNS FamilyShield offer this without additional software
- You are isolating a troubleshooting variable and need a known-good external resolver to rule out SaskTel's infrastructure
Google's Public DNS documentation covers per-platform setup instructions if you decide to switch permanently.
2026 Notes on IPv6, DoH, and DNSSEC
IPv6 DNS: SaskTel has been rolling out dual-stack IPv6 to residential customers in stages. If your connection has an IPv6 address, your modem advertises an IPv6 DNS server via DHCPv6 or Router Advertisement alongside the IPv4 resolvers. On Linux, resolvectl status lists all DNS servers including IPv6 ones. If the IPv6 DNS entry is missing or incorrect, devices may fail to resolve AAAA records for IPv6-preferred domains even though IPv4 DNS is functioning perfectly — a subtle failure mode that looks like a slow or intermittent connection.
DNS-over-HTTPS (DoH): Windows 11 build 22H2 and later, macOS Ventura and later, and Firefox 124+ all support DoH natively. When DoH is enabled at the OS or browser level, the system bypasses ISP resolvers entirely and routes queries to the configured DoH provider. This also bypasses any filtering SaskTel applies at the resolver layer. If browsing behavior changed unexpectedly after a Windows update or browser update, check Settings → Privacy → DNS over HTTPS in Firefox and the Windows Settings → Network & Internet → Ethernet → Edit → Encrypted DNS option.
DNSSEC: SaskTel's resolvers support DNSSEC validation. Verify this from the command line:
If dnssec-failed.org returns actual answers instead of SERVFAIL, DNSSEC validation is not active on that resolver path.
Confirming the Fix Worked
- Flush the DNS cache on the device using the commands above for your OS
- Query both resolvers directly and confirm valid IPs are returned: dig @208.75.76.3 google.com +short and dig @208.75.76.4 google.com +short
- Run nslookup google.com without a specified server — the Server line should show 208.75.76.3 or your router's LAN IP
- Open a browser and load a domain that was previously failing
If step 3 shows an unexpected server, something else is still overriding your DNS configuration. Check for an active VPN client, a browser with DoH enabled, or a network management policy on corporate or school devices pushing its own DNS settings.
Preventing DNS Problems from Recurring
- Always configure both primary and secondary DNS — single-server setups fail completely during any outage on that one server with no fallback
- Set DNS at the router level rather than per-device so new devices automatically inherit correct settings
- For any device with a static IP address, manually enter both DNS IPs — DHCP-delivered DNS does not apply to statically configured interfaces
- Keep router firmware updated; outdated firmware has documented bugs in DNS relay behavior and DHCP lease handling
- Consider adding a public fallback such as 1.1.1.1 as a tertiary DNS entry at the router level so a SaskTel resolver outage does not leave the entire network without name resolution