Skip to main content

Configure a DNS resolver

Plain DNS sends queries unencrypted over UDP or TCP on port 53. No additional software is required — configure the resolver address directly in network settings. DoH and DoT encrypt queries in transit and are supported on the same operating systems.

Use the following CDB Public DNS resolver addresses in the configuration steps below:

  • IPv4: 95.85.95.85 and 2.56.220.2
  • IPv6: 2a03:90c0:999d::1 and 2a03:90c0:9992::1

The instructions below show IPv4 configuration. Where the operating system supports dual-stack DNS, add the IPv6 addresses through the IPv6 DNS settings on the same screen.

Configure the resolver

Set the DNS server for a specific network adapter. The change applies to all connections through that adapter.

Settings (Windows 10 and 11)

  1. Open Settings > Network & internet.
  2. Select Wi-Fi or Ethernet, then click the active connection name.
  3. Scroll to DNS server assignment and select Edit.
  4. Change the dropdown to Manual.
  5. Enable the IPv4 toggle.
  6. Set Preferred DNS to 95.85.95.85 and Alternate DNS to 2.56.220.2.
  7. Select Save.

PowerShell (Windows 10 and 11)

Run Get-NetAdapter to list adapter names, then apply the resolver addresses:

Get-NetAdapter
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses "95.85.95.85","2.56.220.2"

Replace Wi-Fi with the actual adapter name if different.

Verify

nslookup example.com

The Server: line should show 95.85.95.85. If it shows a different IP, the adapter setting was not saved or another adapter is being used.

DNS settings on macOS apply per network interface. Repeat these steps for each interface in use (Wi-Fi, Ethernet).

  1. Open System Settings > Network.
  2. Select the active interface and click Details.
  3. Open the DNS tab.
  4. Click + and add 95.85.95.85, then add 2.56.220.2.
  5. Click OK and then Apply.

Verify

nslookup example.com

The Server: line should show 95.85.95.85.

Select the method based on how the system manages network connections.

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

  1. Edit /etc/systemd/resolved.conf:

    [Resolve]
    DNS=95.85.95.85 2.56.220.2
    
  2. Restart the service:

    sudo systemctl restart systemd-resolved
    
  3. Verify:

    resolvectl status
    

    The current DNS server for the interface should show 95.85.95.85.

NetworkManager

nmcli connection modify <connection-name> ipv4.dns "95.85.95.85 2.56.220.2"
nmcli connection modify <connection-name> ipv4.ignore-auto-dns yes
nmcli connection up <connection-name>

Replace <connection-name> with the output of nmcli connection show.

Verify

nmcli dev show | grep DNS

The output should list 95.85.95.85 as the active DNS server.

resolv.conf (manual fallback)

Use this method only if neither systemd-resolved nor NetworkManager is available. Add to /etc/resolv.conf:

nameserver 95.85.95.85
nameserver 2.56.220.2

DHCP clients overwrite this file on reconnect. This is not a persistent configuration — use systemd-resolved or NetworkManager instead where possible.

Android applies DNS settings per Wi-Fi network, not system-wide. Mobile data DNS cannot be changed without encrypted DNS or a VPN. Private DNS provides system-wide DoT configuration that covers both Wi-Fi and mobile data.

  1. Open Settings and navigate to the Wi-Fi settings.
  2. Tap and hold the connected network, then select Modify network or tap the gear icon.
  3. Expand Advanced options.
  4. Change IP settings to Static.
  5. Set the primary DNS to 95.85.95.85 and secondary DNS to 2.56.220.2.
  6. Save.

Reopen the connection settings and confirm the DNS addresses are saved. Android does not provide a built-in DNS lookup tool, so confirming the saved settings is the available configuration check.

iOS applies DNS settings per Wi-Fi network. Mobile data DNS is not configurable at the system level. Firefox on iOS supports DoH and DoT configuration through its browser settings.

  1. Open Settings > Wi-Fi.
  2. Tap the (i) next to the connected network.
  3. Scroll to Configure DNS and select Manual.
  4. Remove existing DNS entries and add 95.85.95.85 and 2.56.220.2.
  5. Tap Save.

Reopen the network settings and confirm the DNS entries are saved. iOS does not provide a built-in DNS lookup tool, so confirming the saved settings is the available configuration check.

Setting DNS on the router applies CDB Public DNS to all devices on the network without per-device configuration.

pfSense / OPNsense

  1. Navigate to System > General Setup.
  2. Under DNS Servers, enter 95.85.95.85 and 2.56.220.2.
  3. Click Save.

ASUS routers

  1. Open WAN > Internet Connection.
  2. Set the primary DNS to 95.85.95.85 and secondary DNS to 2.56.220.2.
  3. Click Apply.

Other routers

Look for DNS settings in the WAN or Internet connection section of the router admin panel. Enter 95.85.95.85 as the primary DNS and 2.56.220.2 as the secondary DNS.


After saving, verify from a device connected to the router:

nslookup example.com

The Server: line shows the router's LAN IP — this is expected, as devices send queries to the router, which forwards them to CDB. Confirm the router's DNS settings show 95.85.95.85 in the admin panel to verify the upstream is configured correctly.