How to Change DNS Settings on a D-Link COVR Mesh System

D-Link COVR mesh systems distribute DNS in two distinct places: at the WAN interface where your router communicates with the ISP, and at the LAN/DHCP layer where it instructs every connected device which resolver to query. Most slow-lookup complaints, split-resolution bugs, and the classic "DNS works on my laptop but not my phone" pattern trace directly to one of these two settings — or to changes being made on the wrong node entirely. This guide walks through every current COVR model's admin panel, the exact menu paths, CLI verification commands, and the five most common misdiagnoses that waste hours of troubleshooting time.

Why DNS on a Mesh Router Behaves Differently

In a traditional single-router setup, there is one place to change DNS. A D-Link COVR mesh adds satellite nodes that operate as wireless access points, bridging traffic back to the primary node. The satellites do not run their own DHCP server or DNS forwarder — those functions live exclusively on the primary node. That means every DNS change must happen on the primary node, but it affects every device across every satellite's coverage zone.

The consequence: if you have been logging into a satellite's IP address and making DNS changes there, the settings silently do nothing. You will save successfully, the UI will not complain, and your DNS will remain broken. Identify your primary node — it is the one with an Ethernet cable running to your modem or ONT — and make all changes there.

D-Link COVR Models and Their Admin URLs

The correct admin address varies by model and firmware vintage. Use the right one for your hardware:

• COVR-1100 / COVR-1102 / COVR-1103 — http://192.168.0.1 via browser, or the D-Link Wi-Fi app
• COVR-2202 — http://192.168.0.1; some firmware revisions also respond at http://dlinkrouter.local
• COVR-X1870 / COVR-X1872 — http://192.168.0.1 or http://covr.local; Wi-Fi 6 models with a revised UI introduced in firmware 1.03
• COVR-X3870 — http://192.168.0.1; tri-band Wi-Fi 6 using the same revised UI as the X1870 series

If the browser returns nothing at 192.168.0.1, your gateway may be on a different subnet. Run ipconfig /all on Windows or ip route show default on Linux — the Default Gateway line shows the address to target.

Logging In and Finding DNS Settings

Open a browser on any device connected to the COVR network — wired is most reliable — and navigate to http://192.168.0.1. Default credentials are printed on the router label: typically username admin with a blank or "admin" password on older units, or a unique printed password on newer hardware. If the password is unknown, hold the reset button on the rear for 10 seconds until the LED flashes amber to restore factory defaults.

The D-Link Wi-Fi app (iOS and Android) exposes the same settings and works well for basic resolver changes. However, advanced DHCP fields and IPv6 DNS options only appear in the full web UI, so use the browser when you need complete control over the configuration.

Changing WAN DNS (What the Router Uses Upstream)

WAN DNS is what the router itself queries for NTP time sync, dynamic DNS updates, firmware check-in, and any web filtering enabled at the router level. By default it is set to automatic, using your ISP's resolver. To override it:

1. Log in to http://192.168.0.1
2. Click the Settings icon (gear icon in the top navigation bar)
3. Select Internet
4. Scroll to the DNS Settings section below your connection type (Dynamic IP, PPPoE, or Static IP)
5. Uncheck Obtain DNS server address automatically
6. Enter your Primary DNS and Secondary DNS addresses
7. Click Save and wait a few seconds for the change to apply

Popular public resolvers: Cloudflare (1.1.1.1 / 1.0.0.1), Google (8.8.8.8 / 8.8.4.4), Quad9 with malware blocking (9.9.9.9 / 149.112.112.112). Cloudflare for Families uses 1.1.1.3 / 1.0.0.3 for family-safe filtering without installing anything on devices.

Changing LAN DHCP DNS (What Gets Pushed to Every Device)

This is the setting that matters for most users. DHCP DNS is distributed to every connected device via DHCP leases — phones, laptops, smart TVs, IoT devices. By default the COVR hands out its own LAN IP (192.168.0.1) as the DNS server, meaning client queries go to the router and the router forwards them upstream. If you want devices to hit a public or private resolver directly and bypass the router's cache, put those resolver IPs here instead.

Path in current COVR firmware (1.03+ on X-series, equivalent layout on older models):

1. Log in, click Settings
2. Select Network
3. Click DHCP (labeled LAN in pre-2020 firmware)
4. Find the Primary DNS Server and Secondary DNS Server fields
5. Enter your resolver IPs
6. Click Save

After saving, existing client leases retain the old DNS server address until the lease expires. The default lease time on COVR units is 1440 minutes (24 hours). Force a renewal immediately rather than waiting:

Older COVR Firmware (Pre-2020 Flat Menu)

Units running firmware from 2018–2019 use a flat menu without the gear-icon layout. The equivalent paths are Setup > Internet Connection for WAN DNS and Setup > Network Settings for LAN DHCP DNS. Field names are identical. If your admin UI does not match the current layout, update firmware first — navigate to Tools > Firmware or Management > Firmware > Check for Updates. Several DNS forwarding bugs and a DHCP relay issue affecting satellite nodes were patched between firmware 1.01 and 1.05 on the COVR-1100 series; running old firmware before troubleshooting DNS is a common waste of time.

CLI Verification After Changing DNS

The router's save confirmation does not tell you whether client devices actually picked up the change. Verify directly from the client machine:

On Windows, the Server: line in nslookup output shows exactly which resolver answered the query. If it still shows your ISP's IP after forcing a DHCP renewal and flushing the cache, reboot the device — Windows sometimes holds a cached DNS assignment through a renewal cycle without actually switching resolvers.

Per-Device DNS on Windows, Mac, Linux, iOS, and Android

When you need one device to use a different resolver without touching the router — useful for testing a new provider or applying parental controls to a single machine — override DNS at the OS level:

Windows 11

1. Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties
2. Click Edit next to DNS server assignment
3. Switch to Manual, enable IPv4, enter resolver IPs

macOS Sonoma and Sequoia

1. System Settings > Wi-Fi > click your network name > Details > DNS
2. Click + to add resolver IPs; delete the grayed-out DHCP-supplied entry

Linux (systemd-resolved)

iOS 17 and 18

1. Settings > Wi-Fi > tap the (i) next to your network name
2. Scroll to Configure DNS > tap Manual
3. Delete existing server entries, then add your resolver IPs

Android 10 and Later

Android supports system-wide Private DNS (DNS-over-TLS) independently of DHCP: Settings > Network & Internet > Private DNS > enter a hostname such as dns.cloudflare.com or dns.google. This overrides DHCP-pushed DNS for all connections and encrypts queries in transit, bypassing ISP-level interception on port 53 entirely.

IPv6 DNS, DoH, DoT, and DNSSEC on COVR in 2026

IPv6 deployment has accelerated significantly in 2026 and introduces a subtle DNS trap. If your ISP provides IPv6 connectivity, your COVR receives DHCPv6 or SLAAC configuration that includes IPv6 DNS server addresses. Devices with IPv6 connectivity may completely ignore your IPv4 DNS settings and use the IPv6 resolver provided by the ISP instead. This is currently the most frequent root cause of "I changed DNS and nothing happened" on residential mesh networks with IPv6 enabled.

To check and fix: navigate to Settings > Internet > IPv6. If IPv6 is enabled with automatic DNS, ISP-assigned IPv6 resolvers are being distributed alongside your custom IPv4 ones. Uncheck automatic DNS and enter IPv6 resolver addresses manually. Cloudflare: 2606:4700:4700::1111 and 2606:4700:4700::1001. Google: 2001:4860:4860::8888 and 2001:4860:4860::8844. If you do not need IPv6, disable it entirely in the same screen — devices fall back to IPv4 DNS and your custom settings apply cleanly without IPv6 resolver interference.

DoH and DoT: COVR firmware does not natively support DNS-over-HTTPS or DNS-over-TLS on the router itself as of 2026. For encrypted DNS across the whole network, run a local resolver such as cloudflared in proxy mode, Unbound, or AdGuard Home on a Raspberry Pi or small server on the LAN, point COVR DHCP DNS to that host's static LAN IP, and configure it to forward queries over DoT or DoH upstream. Per-device, Android's Private DNS and Apple's DoH configuration profiles handle encrypted DNS without requiring any router changes at all.

DNSSEC: The COVR's built-in DNS forwarder passes DNSSEC signatures through to clients but does not validate them itself. For DNSSEC validation, use a validating resolver upstream: Cloudflare (1.1.1.1), Google (8.8.8.8), and Quad9 (9.9.9.9) all perform DNSSEC validation by default. If running a local Unbound instance, set val-permissive-mode: no to enforce strict validation and reject responses with broken DNSSEC signatures.

Five Common Misdiagnoses

1. Editing DNS on a Satellite Node

COVR satellite nodes show a fully functional admin panel when you access their LAN IP. The DNS and DHCP fields accept input and save without error — but the changes have no effect on clients whatsoever. Satellites operate as wireless access points and inherit all network settings from the primary node. Every DNS change must go on the primary node connected to your modem or ONT, not on any satellite.

2. DHCP Lease Not Refreshed

After changing DHCP DNS on the router, devices hold their old lease — including the old DNS server address — until it expires (default 24 hours on COVR) or is manually released and renewed. This is the single most common reason a DNS change appears to do nothing immediately. Force a DHCP renewal on your test device using the commands in the section above, then re-run nslookup to verify the resolver actually changed.

3. Browser DNS Cache

Chrome and Firefox maintain their own DNS caches independently of the operating system. After flushing the system DNS cache and renewing the DHCP lease, browsers may still serve stale records for domains they have recently resolved. In Chrome, navigate to chrome://net-internals/#dns and click Clear host cache. Firefox clears its DNS cache on a full browser restart.

4. ISP Transparent DNS Hijacking

Some ISPs intercept all outbound UDP traffic on port 53 and redirect it to their own resolvers regardless of what you have configured. If running nslookup google.com 1.1.1.1 returns a result but the answering server IP belongs to your ISP's address space, interception is active. The fix is encrypted DNS transport — DoT on port 853 or DoH on port 443 — which ISP-level interception cannot redirect without breaking broad HTTPS traffic in the process.

5. COVR Running in Access Point Mode

If the primary COVR is configured in Access Point mode to preserve an upstream router's IP scheme, the COVR stops running DHCP and stops distributing DNS to clients entirely. Its DNS settings have no effect in this mode. Make DNS changes on the upstream device — your ISP gateway, business firewall, or standalone router — instead.

Confirming the Fix Worked

1. nslookup or dig on a client device — the Server: line should display your new resolver's IP, not your ISP's address
2. DNS leak test — run an extended test on any DNS leak testing site; all results should show infrastructure belonging to your chosen resolver, not your ISP
3. Latency check — a second dig google.com should return a noticeably lower query time than the first run, confirming the resolver's cache is responding and functioning normally

Preventing Future DNS Problems on Your COVR Mesh

• Keep COVR firmware current by checking Management > Firmware > Check for Updates — D-Link has released DNS-specific fixes in minor firmware revisions that are easy to miss
• Always set both a primary and secondary DNS resolver; a mesh with a single resolver entry will stall all DNS lookups if that upstream has any outage
• Document your DNS configuration before any factory reset, which clears all custom DNS entries without warning
• If running a local DNS resolver such as Pi-hole or AdGuard Home, assign it a static DHCP reservation under Settings > Network > DHCP > Add Static IP so its LAN address never changes and breaks all client resolution
• After any major firmware upgrade, re-verify DNS settings — some COVR firmware versions have silently reverted custom DNS entries back to automatic on update

For a thorough reference on how DNS resolution works end-to-end — from your router's cache through the recursive resolver chain to authoritative name servers — the original DNS specification RFC 1035 provides the technical foundation. Understanding the full resolution chain clarifies why router-level DNS changes propagate differently from registrar-level changes, and why DHCP lease timing determines how quickly those changes actually reach your devices.